On Thu, 30 Oct 2003, Jonathan Giles wrote: > in squid.conf in ver. 3, these are the options I have made: > ---- > https_port 443 cert=/etc/openssl/cacert.pem > key=/etc/openssl/privkey.pem accel defaultsite=owa.clinedavis.com > > cache_peer owa.clinedavis.com parent 80 0 no-query front-end-https=on > --- > in /etc/hosts > --- > 10.1.16.67 owa.clinedavis.com > --- > and when I go to the squid server I get this... > > Bad Request (Invalid URL)
Hmm.. you should not be seeing this error. > in access.log I get this > > 1067539553.232 1 10.1.16.100 TCP_NEGATIVE_HIT/400 270 GET > https://owa.clinedavis.com/ - NONE/- text/html What was the first entry? This is a cache hit for an error which occurred earlier. > 1067543543.673 23 10.1.16.100 TCP_MISS/400 262 GET > https://owa.clinedavis.com/ - FIRST_UP_PARENT/owa.clinedavis.com > text/html This looks better. > when I change the ip in etc/hosts to some other web server, it works. Does the OWA server listen on 10.1.16.67 port 80? Note: You do not need to specify the server by name in cache_peer. Using IP addresses is fine here. > In squid2 this following config works, but still has that not loading > folders problem. What URL is the client asking for? For this to work the client must be asking for https://owa.clinedavis.com/ Regards Henrik
