W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: Issue 196, was: #110: how to determine what entity a response carries

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 15 Apr 2010 14:13:14 +0200
Message-ID: <4BC702DA.50609@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>, =JeffH <Jeff.Hodges@KingsMountain.com>
On 15.04.2010 04:03, Mark Nottingham wrote:
> I think it would be helpful to have an example with an explicit port number. Also, the proposed text refers to 'host name', which isn't quite right.

Ack. Update at 
<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/196/i196.diff>. 
Now uses "authority" instead of "host":

-- snip --
4.3.  Effective Request URI

    The term "Effective Request URI" is introduced in order to abstract
    away the various syntactical forms a request can take.

    If the request-target is an absolute-URI, then the Effective Request
    URI is the request-target. [[effrequri-scheme: What about the case
    where the given scheme name and the transport disagree?  What if
    actual and specified port disagree? --jre]]

    If the request-target uses the path-absolute (plus optional query)
    syntax, then the Effective Request URI is constructed by
    concatenating

    o  the scheme name: "http" if the request was received over an
       insecure TCP connection, or "https" when received over SSK/
       TLS-secured TCP connection, [[effrequri-othertransports: Need to
       mention other future transports here? --jre]]

    o  the character sequence "://",

    o  the authority component, as specified in the Host header
       (Section 9.4) and determined by the rules in Section 4.2,
       [[effrequri-nohost: How do we deal with undefined hosts? --jre]]
       and

    o  the request-target obtained from the Request-Line.

    Otherwise, when request-target is an asterisk ("*") or uses the
    authority form, the Effective Request URI is undefined.

    Example: the Effective Request URI for the message

      GET /pub/WWW/TheProject.html HTTP/1.1
      Host: www.example.org:8080

    (received over an insecure TCP connection) is "http", plus "://",
    plus the authority component "www.example.org:8080", plus the
    request-target "/pub/WWW/TheProject.html", thus
    "http://www.example.org:8080/pub/WWW/TheProject.html".

    [[effrequri-compare: Need to declare comparison?  Can we re-use the
    comparison defined in Section 2.6.3? --jre]]
-- snip --

Best regards, Julian
Received on Thursday, 15 April 2010 12:13:56 GMT

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