On 5/3/06, Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx> wrote:
ons 2006-05-03 klockan 05:02 -0400 skrev Sketch: > Hey Folks, > > I've got squid + rproxy patch applied running with a couple > cache_peer's controlled by cache_peer_access and acls. > > Running into a little problem when attempting to load a page: > > ERROR > The requested URL could not be retrieved > * Invalid Request Have you set your http_port parameters correct? The rproxy patch changes a bit how you set up Squid as an accelerator.
It works for http connections now, but not https: Same error page as before, with this output for the request: GET /admin/ HTTP/1.1 User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.2 (like Gecko) (Debian) Accept: text/html, image/jpeg, image/png, text/*, image/*, */* Accept-Encoding: x-gzip, x-deflate, gzip, deflate Accept-Charset: iso-8859-1, utf-8;q=0.5, *;q=0.5 Accept-Language: en Host: something.wicked.com Connection: Keep-Alive The squid log shows: 2006/05/03 07:57:46| clientReadRequest: FD 13 Invalid Request My https line looks like: https_port 123.123.123.123:443 cert=/usr/local/squid/etc/ssl/wicked.com.crt key=/usr/local/s quid/etc/ssl/wicked.com.key Any ideas?
