Re: [squid-users] redirection to https not working

My guess is that your redirection to https:// triggers even if the client is
actually requesting https://...

I haven't tested if the redirectors can see any difference between the
http_port and https_port in plain Squid-2.5. Probably not as there only is a
single set of httpd_accel_... directives that applies to all ports. This is
one of the areas I rewrote heavily in the rproxy patch to make these
things easier...

Regards
Henrik

joaquin.domenech@dutchtone.nl wrote:
> Hi Henrik,
>
> thanks for your reply. I enabled log_mime_hdrs as you told me and i can see
> how squid is redirecting the client to https with a location tag. I've been
> snooping the connection and this is what it happens:
> (snooping from the squid server exgate-test)
>
> 16 0.00111 10.144.24.198 -> exgate-test-01 HTTP GET / HTTP/1.1
> 17 0.00016 exgate-test-01 -> 10.144.24.198 HTTP R port=1852
> 18 0.00221 exgate-test-01 -> 10.144.24.198 HTTP HTTP/1.0 302 Moved
> Temporarily ---> that's the wanted behaviour but....
> 19 0.00423 10.144.24.198 -> exgate-test-01 HTTPS C port=1851
> 20 0.00250 exgate-test-01 -> 10.144.24.198 HTTPS R port=1851
> 21 0.00549 10.144.24.198 -> exgate-test-01 HTTPS C port=1851
> [... to the infinite]
>
> during this never end conversation between the proxy and the client i also
> snooped in the final server and i couldn't see any traffic.
> Any idea ?
> Could you please tell me if you have ever configured this way, squid2.5 in
> accelerator mode with several servers on port 80 and several of them of 443
> ?
> looks like without redirection everything can work together.
>
> Thanks a lot for your help.

-- 
Basic free Squid support provided thanks to MARA Systems AB
Your source of advanced reverse proxy solutions or customized
Squid solutions. http://www.marasystems.com/products/