Looks like squid doesn't like the virtual port in this version. [EMAIL PROTECTED] root]# squid -k reconfigure FATAL: Bungled squid.conf line 2061: httpd_accel_port virtual Squid Cache (Version 2.5.STABLE3): Terminated abnormally.
Also, if this is true: >> when I add the cache_peer line, all proxy requests start going to >> the ip address of the cache_peer server, no matter what the host >> name is in the redirector... >Yes, this is how it is supposed to work when using cache_peer. Can you still have squid redirect to more than one server? If so, how? Is there a cache_peer virtual? Thanx again, David -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Wed 8/13/2003 4:41 PM To: David Gibson; [EMAIL PROTECTED] Cc: Subject: Re: [squid-users] bungling my squid.conf for front-end-https=on, OWA On Wednesday 13 August 2003 22.19, David Gibson wrote: > OK - edited the perl script to examine the redirection. It looks > ok- strange thing though- all redirector data comes in as http, > even though I'm connecting on port 443. Yes. Squid-2.5 does not make any difference. What you can do is to enable httpd_accel_port virtual This will make the URLs received via https_port look like http://httpd_accel_host:443/... allowing redirectors to see a difference between the two. Alternatively you can edit the source and make Squid reconstruct the url using https:// when the request was received via a https_port but it is probably easier to just use Squid-3.0 where you have direct control over this from squid.conf. > when I add the cache_peer line, all proxy requests start going to > the ip address of the cache_peer server, no matter what the host > name is in the redirector... Yes, this is how it is supposed to work when using cache_peer. > #cache_peer my.server parent 443 80 no-query front-end-https=on > > By the way, is the order "443 80" correct, if 443 is the port the > proxy is listening on, and 80 is the port the web servers are > listing on? The second port number is supposed to be the ICP port. This port is not used when you use the no-query cache_peer option. I usually use 0 in this field in combination with no-query to clearly indicate the field is not used. Port 443 is probably not correct unless you also turn on the ssl cache_peer flag. Regards Henrik
