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

Hi,

I am testing a product called Finjan, which is a website
anti-virus/malicious code checker that potentially blocks websites. I'm
using Squid.2.6-STABLE-12 on an IBM x345 server, with RedHat ES3.0, and have
configured the following fields to make the Finjan appliance a parent proxy
to my Squid setup.

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

Squid Cache (Version 2.6.STABLE12): Terminated abnormally.
CPU Usage: 0.006 seconds = 0.001 user + 0.005 sys
Maximum Resident Size: 0 KB
Page faults with physical i/o: 0
Aborted

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?

Thanks, Ric
Received on Wed Feb 20 2008 - 12:58:18 MST