Ignore:
Timestamp:
Sep 6, 2010, 8:49:57 AM (9 years ago)
Author:
julian.reschke@…
Message:

State that the effective request URI is undefined if you don't know the host (see #221)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r991 r992  
    16801680<t>
    16811681   If the request-target uses the path-absolute form or the asterisk form,
    1682    then the effective request URI is constructed by concatenating
     1682   and the Host header field is present, then the effective request URI is
     1683   constructed by concatenating
    16831684</t>
    16841685<t>
     
    16941695    <t>
    16951696      the authority component, as specified in the Host header field
    1696       (<xref target="header.host"/>) and determined by the rules in
    1697       <xref target="the.resource.identified.by.a.request"/>,
    1698       <cref anchor="effrequri-nohost" source="jre">Do we need to include the handling of missing hosts in HTTP/1.0 messages, as
    1699       described in <xref target="the.resource.identified.by.a.request"/>? -- See <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/221"/></cref>
    1700       and
     1697      (<xref target="header.host"/>), and
    17011698    </t>
    17021699    <t>
     
    17051702    </t>
    17061703  </list>
     1704</t>
     1705<t>
     1706   If the request-target uses the path-absolute form or the asterisk form,
     1707   and the Host header field is not present, then the effective request URI is
     1708   undefined.
    17071709</t>
    17081710<t>
     
    56575659<section title="Since draft-ietf-httpbis-p1-messaging-11" anchor="changes.since.11">
    56585660<t>
    5659   None yet.
     5661  Closed issues:
     5662  <list style="symbols">
     5663    <t>
     5664      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/221"/>:
     5665      "effective request URI: handling of missing host in HTTP/1.0"
     5666    </t>
     5667  </list>
    56605668</t>
    56615669</section>
Note: See TracChangeset for help on using the changeset viewer.