On 13/06/2013 12:58 p.m., opti2k4 wrote:
Amos Jeffries-2 wrote
Please start with details of what that failure is. Any delay could
simply be Squid trying various ways to workaround configuration
mistakes. 9 of your 12 https_port lines are telling Squid to do
impossible things (open a port which is already in use).
Amos
Um i lost you. How can use it that for reverse proxy multiple sites on port
443 (different server) the right way?
At present the only certain way to do it is with multiple IP addresses
on the proxy each listening on port 443 and relaying with squid ACLs to
whichever backend is needing to receive it.
Once someone sorts out for good how the SSL dynamic generation or SNI
can work for reverse-proxy things will be better. For now that is
experimental in 3.3 and later.
Amos
