With virtual hosting, the client is asking for a virtual origin server's host and DNS enables the ip address for the physical host to respond. The virtual host still sees "its" hostname in the host header, not the physical host's.
With a reverse proxy, the backend origin server doesn't see its Host name, it sees the proxy's, even though the proxy is an http client with respect to the origin server.
Antony Stone ---06/12/2015 10:14:32 AM---On Friday 12 June 2015 at 16:08:59 (EU time), Julianne Bielski wrote: > reverse proxies are always "
From: Antony Stone <Antony.Stone@xxxxxxxxxxxxxxxxxxxx>
To: squid-users@xxxxxxxxxxxxxxxxxxxxx
Date: 06/12/2015 10:14 AM
Subject: Re: reverse proxies and Host request header
Sent by: "squid-users" <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx>
On Friday 12 June 2015 at 16:08:59 (EU time), Julianne Bielski wrote:
> reverse proxies are always "transparent" from the perspective of
> the client and the Host header is often used by the proxy
> to map to the correct back end origin server.
>
> I also think they usually pass the Host header as-is to the origin server.
> This last piece puzzles me because it means that the origin server is being
> given a different host name than itself in the header. Is this behavior
> "correct"? Does it ever cause problems?
How is this different from a normal web server serving multiple virtual host
sites?
The web server doesn't care who "it" is, it just cares which virtual host it's
being asked to serve pages for. A reverse proxy in the way basically makes no
difference.
Regards,
Antony.
--
All generalisations are inaccurate.
Please reply to the list;
please *don't* CC me.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
