On 01.11.2012 10:48, Karl Hill wrote:
Hello, I'm having some issues setting up a reverse proxy in my
environment for some URL's running on the same Apache server. I'm
using squid 3.1.10. My configuration is below, but basically I have
two sites on one Apache server and that server is in an isolated
environment. The Apache sites are vhost1 and vhost2.example.com, but
I
need to get to them via the outside.example.com domain. So
effectively:
client -> vhost1.outside.example.com -> squid -> vhost1.example.com
->
apache server
for both. The problem is that only the vhost1 is working. When I go
to
vhost2.outside.example.com I go to vhost1.example.com.
Any help would be appreciated.
Virtual HTTPS hosts have not had much use in Squid and thus not much
testing or feature development. The main problem as I understand it is
that the certificate is a static cert for only one of the domains,
possibly a wildcard cert can make it kind of useful for sub-domains. The
3.1 and older Squid also do not support the TLS SNS feature necessary
for proxies to identify the virtual domain FQDN up front.
Squid-3.2 and later provide a certificate generation feature that it
should be very useful for virtual hosting with HTTPS. Are you able to
upgrade and test it out? There are a few wrinkles due to it being quite
new and not much tested in reverse-proxy, but if it works for you it
would be good to know that - or any issues you can find.
Amos
