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.
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... #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? David -----Original Message----- From: David Gibson Sent: Wed 8/13/2003 3:24 PM To: Henrik Nordstrom; [EMAIL PROTECTED] Cc: Subject: RE: [squid-users] bungling my squid.conf for front-end-https=on, OWA OK- what's the best way to see what's being passed to the redirector? I've tried squid -d9, tailing the cache.log, etc- is it just to edit the perl script that I'm using for a redirector, and have it write the input/output somewhere? Thanx, David -----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Wed 8/13/2003 2:05 PM To: David Gibson; [EMAIL PROTECTED] Cc: Subject: Re: [squid-users] bungling my squid.conf for front-end-https=on, OWA The SSL update does not change how cache_peer deals with Host based virtual domains. What may have changed however is the input to your redirector as the https_port directive knows a little more about https.. Regards Henrik On Wednesday 13 August 2003 18.55, David Gibson wrote: > Hello again, > > I've now successfully patched and recompiled, and the > front-end-https option is working. But... Virtual host support no > longer appears to be working. I had a redirector that was working > with http && https before using the cache_peer option. I'm guessing > that the cache peer option over-rides the ssl traffic redirection- > is that true? > > Is there a simialr cache-peer virtual command, or other workaround? > I have one owa box, and one generic web server- I'm trying to do > https from client to proxy, http from proxy to server... > > Thanx, > > David > > > -----Original Message----- > From: David Gibson > Sent: Wed 8/13/2003 9:03 AM > To: Henrik Nordstrom; [EMAIL PROTECTED] > Cc: > Subject: RE: [squid-users] bungling my squid.conf for > front-end-https=on, OWA Glad I asked... ;) > > > -----Original Message----- > From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] > Sent: Wed 8/13/2003 2:32 AM > 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 06.00, David Gibson wrote: > > By looking at the contents of the patch, it appears that I'm > > supposed to make the changes in the files listed in accordance > > with the "diffs." So, essentially, I'd be making changes to the > > 17 or so files listed below, and recompiling. Do I have that > > right? > > Yes, that is one way. > > Alternatively and what most people do unless there is a problem > with the patch is to use the patch program to do the edits for you. > The patch program reads diff files and edits files according to the > instructions in the diff file. > > Regards > Henrik
