RE: [squid-users] SSL and Reverse Proxy

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Monday, August 23, 2004 1:05 PM
To: Chris Perreault
Cc: Squid Users
Subject: RE: [squid-users] SSL and Reverse Proxy

On Mon, 23 Aug 2004, Chris Perreault wrote:

> Until you mentioned it I did not notice the second "vhost" in that
> config line. It works but now I wonder why its there too. (If I
> understand your question about "twice" correctly)

Correct. But specifying it twice is no difference than specifying it once so
that does not matter.

My question is why vhost is even specified on a https_port? Are you really
doing domain based virtual hosting on this port to your Squid? Is browsers
able to request https://domain1.example.com/ and
https://domain2.example.com/ and both domain1.example.com and
domain2.example.com resolve to the same IP address of your https_port?
This is what the vhost directive does; enables Host: header based virtual
hosting, the same as NameBasedVirtualHost in apache.

Regards
Henrik

~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~

We do not have multiple domain names pointing to the same IP address, but on
the back-end we do have multiple different servers, each reached via the
string following the domain, ie:
Myweb.com/intranet --> origin intranet server
Myweb.com/extranet --> origin extranet server

I swapped vhost for accel and of course it broke. I added in
defaultsite=myweb.com and of course it now works again, thanks for the
guidance.

The "vhost" implicitly sets "accel", which is why things were functioning
before.
What downsides were there to using vhost instead of accel/defaultsite= ? Is
it just better performance by not checking the host header?

Thanks for the assistance,

Chris
Received on Thu Aug 26 2004 - 06:02:07 MDT