W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

defining "Request-URI", was: #110: how to determine what entity a response carries

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 11 Sep 2009 14:40:10 +0200
Message-ID: <4AAA452A.9060006@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Mark Nottingham wrote:
> ...
> Note that 'request-URI' is used here; however, we need to come up with a 
> term to denote "the URI that can be inferred from examining the 
> request-target and the Host header."
> ...

I think that definition should go into either Part 1, Section 4.1.2 
("request-target") or Section 4.2 ("The Resource Identified by a Request").

request-target allows 4 different formats:

   request-target = "*"
                  / absolute-URI
                  / ( path-absolute [ "?" query ] )
                  / authority

As far as I can tell, Request-URI only needs to be defined for the 2nd 
and 3rd case.

In case #2 it would be the request-target.

In case #3, it would be "http:" + value of host header + request-target.

But then, what about https? Do we need to consider this in this context? 
Or should we potentially not include the scheme, thus just use

   hier-part [ "?" query ]

? (in which case "Request-URI" would be a bad choice of names).

BR, Julian
Received on Friday, 11 September 2009 12:41:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:10 GMT