Ignore:
Timestamp:
Oct 27, 2010, 2:52:38 AM (9 years ago)
Author:
julian.reschke@…
Message:

refer to definition of 'authority form' instead of the ABNF term (see #239)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1062 r1064  
    3333  <!ENTITY use100                     "<xref target='Part1' x:rel='#use.of.the.100.status' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3434  <!ENTITY qvalue                     "<xref target='Part3' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     35  <!ENTITY request-target             "<xref target='Part3' x:rel='#request-target' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3536  <!ENTITY header-accept              "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3637  <!ENTITY header-accept-charset      "<xref target='Part3' x:rel='#header.accept-charset' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    347348<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
    348349  <x:anchor-alias value="absolute-URI"/>
    349   <x:anchor-alias value="authority"/>
    350350  <x:anchor-alias value="Accept"/>
    351351  <x:anchor-alias value="Accept-Charset"/>
     
    378378<figure><!--Part1--><artwork type="abnf2616">
    379379  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in &uri;&gt;
    380   <x:ref>authority</x:ref>     = &lt;authority, defined in &uri;&gt;
    381380  <x:ref>comment</x:ref>       = &lt;comment, defined in &header-fields;&gt;
    382381  <x:ref>Host</x:ref>          = &lt;Host, defined in &uri;&gt;
     
    11491148</t>
    11501149<t>
    1151    When using CONNECT, the request-target &MUST; be an authority; i.e.,
    1152    the host name and port number destination of the requested connection
    1153    separated by a colon:
    1154 </t>
    1155 
    1156 <figure><artwork type="example">
    1157     CONNECT server.example.com:80 HTTP/1.1
    1158     Host: server.example.com:80
     1150   When using CONNECT, the request-target &MUST; be use the authority form
     1151   (&request-target;); i.e., the host name and port number destination of the
     1152   requested connection separated by a colon:
     1153</t>
     1154<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
     1155CONNECT server.example.com:80 HTTP/1.1
     1156Host: server.example.com:80
     1157
    11591158</artwork></figure>
    1160 
    11611159<t>
    11621160   Other HTTP mechanisms can be used normally with the CONNECT method --
     
    11681166   authority to create a tunnel:
    11691167</t>
    1170 
    1171 <figure><artwork type="example">
    1172     CONNECT server.example.com:80 HTTP/1.1
    1173     Host: server.example.com:80
    1174     Proxy-Authorization: basic aGVsbG86d29ybGQ=
     1168<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
     1169CONNECT server.example.com:80 HTTP/1.1
     1170Host: server.example.com:80
     1171Proxy-Authorization: basic aGVsbG86d29ybGQ=
     1172
    11751173</artwork></figure>
    1176 
    11771174<t>
    11781175   Like any other pipelined HTTP/1.1 request, data to be tunnel may be
     
    35583555
    35593556<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.6&gt;
    3560 authority = &lt;authority, defined in [Part1], Section 2.6&gt;
    35613557
    35623558<x:ref>comment</x:ref> = &lt;comment, defined in [Part1], Section 3.2&gt;
     
    35943590; Reason-Phrase defined but not used
    35953591; Status-Code defined but not used
    3596 ; authority defined but not used
    35973592; request-header defined but not used
    35983593; response-header defined but not used
Note: See TracChangeset for help on using the changeset viewer.