Re: [squid-users] Forwarding HTTP and HTTPS Traffic to an Upstream Proxy using Cache_Peer on separate ports

On Wed, 20 Feb 2008 19:57:45 -0000
"Ric Lonsdale" <ric.lonsdale@blueyonder.co.uk> wrote:

<snip>
> However, the Finjan appliance listens on port 8080 for standard HTTP
> traffic, but listens on 8443 for HTTPS (SSL) traffic, and squid
> returns the following error with this setup.
>
> FATAL: ERROR: cache_peer 10.198.1.2 specified twice
<snip>
> cache_peer 10.198.1.2 parent 8080 7 no-query
> cache_peer 10.198.1.2 parent 8443 7 no-query
> acl httptraffic proto HTTP
> acl httpstraffic proto HTTPS
> http_access allow httptraffic
> http_access allow httpstraffic
> cache_peer_access 10.198.1.2 allow httptraffic
> cache_peer_access 10.198.1.2 allow SSL_ports
> never_direct allow all
>
> Is it possible to change the squid.conf settings to send HTTP and
> HTTPS requests to the same upstream Finjan appliance, but on separate
> ports?

You'll be wanting to do the following:

cache_peer 10.198.1.2 parent 8080 7 no-query name=finjanhttp
cache_peer 10.198.1.2 parent 8443 7 no-query name=finjanhttps
<snip>
cache_peer_access finjanhttp allow httptraffic
cache_peer_access finjanhttps allow httpstraffic

hth
Tony
Received on Thu Feb 21 2008 - 00:46:14 MST