Ignore:
Timestamp:
Feb 2, 2008, 5:40:24 AM (12 years ago)
Author:
julian.reschke@…
Message:

Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" -> "trailer-part"), avoid underscore character in rule names ("http_URL" -> "http-URL", "abs_path" -> "path-absolute"), add rules for terms imported from URI spec ("absoluteURI", "authority", "path-absolute", "port", "query", "relativeURI", "host) -- these will have to be updated when switching over to RFC3986; addresses #36.

File:
1 edited

Legend:

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

    r182 r185  
    10271027   and <xref target="RFC1808"/>). This specification adopts the
    10281028   definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
    1029    "host", "abs_path", "query", and "authority" from that specification.
    1030 </t>
     1029   "host", "abs_path", "query", and "authority" from that specification:
     1030</t>
     1031<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="absoluteURI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="path-absolute"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="relativeURI"/><iref primary="true" item="Grammar" subitem="uri-host"/>
     1032  absoluteURI   = &lt;absoluteURI, defined in <xref target="RFC2396" x:fmt="," x:sec="3"/>>
     1033  authority     = &lt;authority, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2"/>>
     1034  path-absolute = &lt;abs_path, defined in <xref target="RFC2396" x:fmt="," x:sec="3"/>>
     1035  port          = &lt;port, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2.2"/>>
     1036  query         = &lt;query, defined in <xref target="RFC2396" x:fmt="," x:sec="3.4"/>>
     1037  relativeURI   = &lt;relativeURI, defined in <xref target="RFC2396" x:fmt="," x:sec="5"/>>
     1038  uri-host      = &lt;host, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2.2"/>>
     1039</artwork></figure>
    10311040<t>
    10321041   HTTP does not place any a priori limit on the length of
     
    10541063   semantics for http URLs.
    10551064</t>
    1056 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http_URL"/>
    1057   http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
     1065<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URL"/>
     1066  http-URL = "http:" "//" uri-host [ ":" port ]
     1067             [ path-absolute [ "?" query ]]
    10581068</artwork></figure>
    10591069<t>
     
    10611071   are that the identified resource is located at the server listening
    10621072   for TCP connections on that port of that host, and the Request-URI
    1063    for the resource is abs_path (<xref target="request-uri"/>). The use of IP addresses
     1073   for the resource is path-absolute (<xref target="request-uri"/>). The use of IP addresses
    10641074   in URLs &SHOULD; be avoided whenever possible (see <xref target="RFC1900"/>). If
    1065    the abs_path is not present in the URL, it &MUST; be given as "/" when
     1075   the path-absolute is not present in the URL, it &MUST; be given as "/" when
    10661076   used as a Request-URI for a resource (<xref target="request-uri"/>). If a proxy
    1067 
    10681077   receives a host name which is not a fully qualified domain name, it
    10691078   &MAY; add its domain to the host name it received. If a proxy receives
     
    10831092    <t>Comparisons of host names &MUST; be case-insensitive;</t>
    10841093    <t>Comparisons of scheme names &MUST; be case-insensitive;</t>
    1085     <t>An empty abs_path is equivalent to an abs_path of "/".</t>
     1094    <t>An empty path-absolute is equivalent to an path-absolute of "/".</t>
    10861095  </list>
    10871096</t>
     
    12371246   received the full message.
    12381247</t>
    1239 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Chunked-Body"/><iref primary="true" item="Grammar" subitem="chunk"/><iref primary="true" item="Grammar" subitem="chunk-size"/><iref primary="true" item="Grammar" subitem="last-chunk"/><iref primary="true" item="Grammar" subitem="chunk-extension"/><iref primary="true" item="Grammar" subitem="chunk-ext-name"/><iref primary="true" item="Grammar" subitem="chunk-ext-val"/><iref primary="true" item="Grammar" subitem="chunk-data"/><iref primary="true" item="Grammar" subitem="trailer"/>
     1248<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Chunked-Body"/><iref primary="true" item="Grammar" subitem="chunk"/><iref primary="true" item="Grammar" subitem="chunk-size"/><iref primary="true" item="Grammar" subitem="last-chunk"/><iref primary="true" item="Grammar" subitem="chunk-extension"/><iref primary="true" item="Grammar" subitem="chunk-ext-name"/><iref primary="true" item="Grammar" subitem="chunk-ext-val"/><iref primary="true" item="Grammar" subitem="chunk-data"/><iref primary="true" item="Grammar" subitem="trailer-part"/>
    12401249  Chunked-Body   = *chunk
    12411250                   last-chunk
    1242                    trailer
     1251                   trailer-part
    12431252                   CRLF
    12441253 
     
    12521261  chunk-ext-val  = token | quoted-string
    12531262  chunk-data     = 1*OCTET ; a sequence of chunk-size octets
    1254   trailer        = *(entity-header CRLF)
     1263  trailer-part   = *(entity-header CRLF)
    12551264</artwork></figure>
    12561265<t>
     
    16171626  Request-URI    = "*"
    16181627                 | absoluteURI
    1619                  | ( abs_path [ "?" query ] )
     1628                 | ( path-absolute [ "?" query ] )
    16201629                 | authority
    16211630</artwork></figure>
     
    16551664   The most common form of Request-URI is that used to identify a
    16561665   resource on an origin server or gateway. In this case the absolute
    1657    path of the URI &MUST; be transmitted (see <xref target="general.syntax"/>, abs_path) as
     1666   path of the URI &MUST; be transmitted (see <xref target="general.syntax"/>, path-absolute) as
    16581667   the Request-URI, and the network location of the URI (authority) &MUST;
    16591668   be transmitted in a Host header field. For example, a client wishing
     
    16791688</t>
    16801689<t>
    1681    A transparent proxy &MUST-NOT; rewrite the "abs_path" part of the
     1690   A transparent proxy &MUST-NOT; rewrite the "path-absolute" part of the
    16821691   received Request-URI when forwarding it to the next inbound server,
    1683    except as noted above to replace a null abs_path with "/".
     1692   except as noted above to replace a null path-absolute with "/".
    16841693</t>
    16851694<t>
     
    24002409</t>
    24012410<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
    2402   Host = "Host" ":" host [ ":" port ] ; <xref target="http.url"/>
     2411  Host = "Host" ":" uri-host [ ":" port ] ; <xref target="http.url"/>
    24032412</artwork></figure>
    24042413<t>
     
    26482657  protocol-name     = token
    26492658  protocol-version  = token
    2650   received-by       = ( host [ ":" port ] ) | pseudonym
     2659  received-by       = ( uri-host [ ":" port ] ) | pseudonym
    26512660  pseudonym         = token
    26522661</artwork></figure>
     
    41724181  </list>
    41734182</t>
     4183<t>
     4184  Other changes:
     4185  <list style="symbols">
     4186    <t>
     4187       Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
     4188       "trailer-part"), avoid underscore character in rule names ("http_URL" ->
     4189       "http-URL", "abs_path" -> "path-absolute"), add rules for terms
     4190       imported from URI spec ("absoluteURI", "authority", "path-absolute",
     4191       "port", "query", "relativeURI", "host) -- these will have to be updated
     4192       when switching over to RFC3986
     4193       (work in progress on <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>)
     4194    </t>
     4195  </list>
     4196</t>
    41744197</section>
    41754198
Note: See TracChangeset for help on using the changeset viewer.