protocol/392: Does not accept absolute URI in request.

[David Hull <hu...@cs.uiuc.edu>]

>Number:         392
>Category:       protocol
>Synopsis:       Does not accept absolute URI in request.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Apr 14 11:20:02 1997
>Originator:     hull@cs.uiuc.edu
>Organization:
apache
>Release:        1.2b8
>Environment:
SunOS pertsserver 5.5.1 Generic_103640-02 sun4m sparc SUNW,Sun_4_600
pertsserver$ gcc --version
2.7.2.1

>Description:
In apache 1.2b8, the request

  GET http://pertsserver.cs.uiuc.edu/ HTTP/1.1

fails, while

  GET / HTTP/1.1
  Host: pertsserver.cs.uiuc.edu

succeeds.  The error log for the first request says:

  [Mon Apr 14 13:15:30 1997] access to / failed for pertsserver.cs.uiuc.edu, reason: client sent HTTP/1.1 request without hostname

My understanding is that they should both succeed.  The HTTP/1.1 
spec (RFC2068) says:

  5.1.2 Request-URI

   [...]
          Request-URI    = "*" | absoluteURI | abs_path

   [...]

   An example Request-Line would be:

          GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1

   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.
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted: