Ok I want the 80 site externally on 443 and the 8080 site accessible externally on a high port of 45678. Is this right? https_port 443 cert=/usr/local/squid/var/cert.pem urlgroup=1 vhost https_port 45678 cert=/usr/local/squid/var/cert.pem urlgroup=2 vhost cache_peer 10.10.59.01 parent 80 0 no-query proxy-only originserver login=PASS n ame=web1-http cache_peer 10.10.59.01 parent 443 0 no-query proxy-only originserver login=PASS name=web1-https cache_peer_access web1-http allow allout2 cache_peer_access web1-https allow allout3 acl allout dst 10.10.59.01/255.255.255.255 acl urlgroup group1 allout2 port 80 acl urlgroup group2 allout3 port 8080 -----Original Message----- From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Tuesday, July 03, 2007 5:34 PM To: Jason Hitt Cc: squid-users@xxxxxxxxxxxxxxx Subject: RE: Muliple ports on single web backend On tis, 2007-07-03 at 10:44 -0500, Jason Hitt wrote: > OK I get that what I don't understand is how squid will know what > ports I put on my cache_peer line will match up with the ports on my > https_port lines? By the cache_peer_access rules.. > -----Original Message----- > From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] > Sent: Monday, July 02, 2007 5:39 PM > To: Jason Hitt > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: RE: Muliple ports on single web backend > > 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 > > 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 > > acl port443 port 443 > > cache_peer_access web1-https allow web1-sites port443 > > Regards > Henrik
