commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: [Fwd: [HttpClient][PATCH] Correction to addHostRequestHeader+minor formatting cleanups]
Date Thu, 11 Jul 2002 15:38:02 GMT


On 11 Jul 2002, Ryan Lubke wrote:

> Date: 11 Jul 2002 09:01:37 -0500
> From: Ryan Lubke <Ryan.Lubke@Sun.COM>
> Reply-To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> Subject: Re: [Fwd: [HttpClient][PATCH] Correction to
>     addHostRequestHeader+minor   formatting cleanups]
>
>
> <snip>
> >    ....Given the rate of growth of
> >    the Web, and the number of servers already deployed, it is extremely
> >    important that all implementations of HTTP (including updates to
> >    existing HTTP/1.0 applications) correctly implement these
> >    requirements:
> >
> >       - Both clients and servers MUST support the Host request-header.
>
> </snip>
>
> I interpreted "including updates to existing HTTP/1.0 applications" to
> mean that updated HTTP/1.0 application could send the Host
> request-header without violating the RFC.
>

>From conversations with Roy Fielding (one of the authors of RFC 2616, and
a board member of the Apache Software Foundation) during development of
Tomcat's HTTP stack, I believe that this is exactly the intention of the
"including updates" clause.  And existing server applications utilize the
"Host" header (if present on an HTTP/1.0 transaction) to implement
software virtual hosting.

That being said, it sounds like a configuration property to turn this on
or off might be useful.

Craig


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message