Changeset 1064 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 27/10/10 09:52:38 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1062 r1064 33 33 <!ENTITY use100 "<xref target='Part1' x:rel='#use.of.the.100.status' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 34 34 <!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'/>"> 35 36 <!ENTITY header-accept "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 36 37 <!ENTITY header-accept-charset "<xref target='Part3' x:rel='#header.accept-charset' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 347 348 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies"> 348 349 <x:anchor-alias value="absolute-URI"/> 349 <x:anchor-alias value="authority"/>350 350 <x:anchor-alias value="Accept"/> 351 351 <x:anchor-alias value="Accept-Charset"/> … … 378 378 <figure><!--Part1--><artwork type="abnf2616"> 379 379 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in &uri;> 380 <x:ref>authority</x:ref> = <authority, defined in &uri;>381 380 <x:ref>comment</x:ref> = <comment, defined in &header-fields;> 382 381 <x:ref>Host</x:ref> = <Host, defined in &uri;> … … 1149 1148 </t> 1150 1149 <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 connection1153 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="request"" x:indent-with=" "> 1155 CONNECT server.example.com:80 HTTP/1.1 1156 Host: server.example.com:80 1157 1159 1158 </artwork></figure> 1160 1161 1159 <t> 1162 1160 Other HTTP mechanisms can be used normally with the CONNECT method -- … … 1168 1166 authority to create a tunnel: 1169 1167 </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="request"" x:indent-with=" "> 1169 CONNECT server.example.com:80 HTTP/1.1 1170 Host: server.example.com:80 1171 Proxy-Authorization: basic aGVsbG86d29ybGQ= 1172 1175 1173 </artwork></figure> 1176 1177 1174 <t> 1178 1175 Like any other pipelined HTTP/1.1 request, data to be tunnel may be … … 3558 3555 3559 3556 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [Part1], Section 2.6> 3560 authority = <authority, defined in [Part1], Section 2.6>3561 3557 3562 3558 <x:ref>comment</x:ref> = <comment, defined in [Part1], Section 3.2> … … 3594 3590 ; Reason-Phrase defined but not used 3595 3591 ; Status-Code defined but not used 3596 ; authority defined but not used3597 3592 ; request-header defined but not used 3598 3593 ; response-header defined but not used
Note: See TracChangeset
for help on using the changeset viewer.