Search squid archive

Re: Muliple ports on single web backend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Henrik Nordstrom wrote:
On Mon, 2007-07-02 at 12:37 -0500, Jason Hitt wrote:
Ok heres what you sent modified for what I want to do, if I put in the
names how will it know my host IP? I'm confused by how this all mates
up.

The internal name for a cache_peer is by default the same as the
specified hostname/ip. To allow for multiple cache_peer lines pointing
to the same host the name= option to cache_peer can be used to assign a
different internal name for that cache_peer line.

Example:

acl web1-sites dstdomain .example.com

cache_peer 192.168.1.2 parent 80 0 no-query originserver web1-http

If I'm not mistaken, this should be...

cache_peer 192.168.1.2 parent 80 0 no-query originserver name=web1-http

acl port80 port 80

cache_peer_access web1-http allow web1-sites port80

cache_peer 192.168.1.2 parent 443 0 no-query ssl originserver web1-https

Same story...

cache_peer 192.168.1.2 parent 443 0 no-query ssl originserver name=web1-https

acl port443 port 443

cache_peer_access web1-https allow web1-sites port443

Regards
Henrik

Chris

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux