httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Finch <>
Subject Re: protocol question, Roy?
Date Sat, 27 Jan 2001 03:12:54 GMT
"Roy T. Fielding" <> wrote:
>> Quick question.  I am testing some of my own stuff, and I have noticed
>> that with Apache 2.0, if I request:
>> GET HTTP/1.0
>> with the server (obviously no proxy module, since it doesn't work), I get
>> the same response as if I just asked for:
>> GET / HTTP/1.0
>> Is that correct?

RFC 2616, section 5.1.2:

   To allow for transition to absoluteURIs in all requests in future
   versions of HTTP, all HTTP/1.1 servers MUST accept the absoluteURI
   form in requests, even though HTTP/1.1 clients will only generate
   them in requests to proxies.


   The most common form of Request-URI is that used to identify a
   resource on an origin server or gateway. In this case the absolute
   path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
   the Request-URI, and the network location of the URI (authority) MUST
   be transmitted in a Host header field.

i.e. we correctly handle absoluteURI requests in origin-server mode,
even though correct clients don't make requests like that.

>> Should we check the host in the request against the hostname of the
>> server?

RFC 2616, section 5.2:

   1. If Request-URI is an absoluteURI, the host is part of the
     Request-URI. Any Host header field value in the request MUST be

I believe (from memory of the last time I looked at the code) we
implement that requirement, i.e. throw away the Host header and treat
the hostname in the request URI as if it were the Host header.

So any checking of the request URI that we do happens as part of the
virtual hosting code.

>We would prefer to send a error of some kind, but that would require
>us to look up (at config time) the entire list of names for this
>server, both for the present and for any legacy names for which we
>are serving as host.


>Likewise, it makes the task of configuring clustered load-balanced
>web servers difficult, and adds a string compare to every request.

The current name-based vhosting code requires O(number of vhosts)
string comparisons per request :-(

>I think it would be legitimate for 2.0 to include a config directive
>that listed all of the host names that this server would allow,

it's calles ServerAlias

>and place those host names in a hash table for fast lookup,
>but I haven't had the urge to do that yet.

Yes, that would be nice :-)

"There are flying saucers. There's no doubt they are
in our skies. They've been there for some time."

View raw message