Changeset 2031 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 05/12/12 16:59:49 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2030 r2031 449 449 } 450 450 @bottom-center { 451 content: "Expires June 7, 2013";451 content: "Expires June 8, 2013"; 452 452 } 453 453 @bottom-right { … … 496 496 <meta name="dct.creator" content="Reschke, J. F."> 497 497 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 498 <meta name="dct.issued" scheme="ISO8601" content="2012-12-0 4">498 <meta name="dct.issued" scheme="ISO8601" content="2012-12-05"> 499 499 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 500 500 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 524 524 <tr> 525 525 <td class="left">Intended status: Standards Track</td> 526 <td class="right">December 4, 2012</td>526 <td class="right">December 5, 2012</td> 527 527 </tr> 528 528 <tr> 529 <td class="left">Expires: June 7, 2013</td>529 <td class="left">Expires: June 8, 2013</td> 530 530 <td class="right"></td> 531 531 </tr> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on June 7, 2013.</p>557 <p>This Internet-Draft will expire on June 8, 2013.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1616 1616 </p> 1617 1617 <p id="rfc.section.5.3.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing 1618 or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 5.7 </a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding1618 or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding 1619 1619 messages in an infinite loop. 1620 1620 </p> … … 3092 3092 </pre><p id="rfc.section.8.4.2.p.4">Example:</p> 3093 3093 <div id="rfc.figure.u.62"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 3094 </pre><p id="rfc.section.8.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7 </a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).3094 </pre><p id="rfc.section.8.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). 3095 3095 </p> 3096 3096 <div class="note" id="rfc.section.8.4.2.p.7"> … … 4155 4155 trust its value. (<a href="#header.allow" id="rfc.xref.header.allow.5" title="Allow">Section 8.4.1</a>) 4156 4156 </p> 4157 <p id="rfc.section.C.p.30">The requirement to generate a <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field has been moved from the description of the <a href="#header.server" class="smpl">Server</a> header field to <a href="p1-messaging.html#header.via" title="Via">Section 5.7 </a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 8.4.2</a>)4157 <p id="rfc.section.C.p.30">The requirement to generate a <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field has been moved from the description of the <a href="#header.server" class="smpl">Server</a> header field to <a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 8.4.2</a>) 4158 4158 </p> 4159 4159 <p id="rfc.section.C.p.31">The contexts that charset is used in have been clarified. (<a href="#charset" title="Charset">Section 3.1.1.2</a>) … … 4171 4171 <p id="rfc.section.C.p.36">The Status Code Registry is now defined by this specification; previously, it was defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 9.2</a>) 4172 4172 </p> 4173 <p id="rfc.section.C.p.37">References to the "identity" transfer -coding valuetoken have been removed. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>)4173 <p id="rfc.section.C.p.37">References to the "identity" transfer coding token have been removed. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>) 4174 4174 </p> 4175 4175 <p id="rfc.section.C.p.38">The Content-Disposition header field is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>) … … 4204 4204 <a href="#header.allow" class="smpl">Allow</a> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ] 4205 4205 4206 <a href="#imported.abnf" class="smpl">BWS</a> = <BWS, defined in [Part1], Section 3.2. 1>4206 <a href="#imported.abnf" class="smpl">BWS</a> = <BWS, defined in [Part1], Section 3.2.3> 4207 4207 4208 4208 <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = *( "," OWS ) content-coding *( OWS "," [ OWS … … 4228 4228 <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*DIGIT 4229 4229 4230 <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 3.2. 1>4231 4232 <a href="#imported.abnf" class="smpl">RWS</a> = <RWS, defined in [Part1], Section 3.2. 1>4230 <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 3.2.3> 4231 4232 <a href="#imported.abnf" class="smpl">RWS</a> = <RWS, defined in [Part1], Section 3.2.3> 4233 4233 <a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI 4234 4234 <a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delta-seconds … … 4250 4250 <a href="#charset" class="smpl">charset</a> = token 4251 4251 <a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*" 4252 <a href="#imported.abnf" class="smpl">comment</a> = <comment, defined in [Part1], Section 3.2. 4>4252 <a href="#imported.abnf" class="smpl">comment</a> = <comment, defined in [Part1], Section 3.2.6> 4253 4253 <a href="#content.codings" class="smpl">content-coding</a> = token 4254 4254 … … 4312 4312 <a href="#product.tokens" class="smpl">product-version</a> = token 4313 4313 4314 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 3.2. 4>4314 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in [Part1], Section 3.2.6> 4315 4315 <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] ) 4316 4316 … … 4322 4322 4323 4323 <a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second 4324 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in [Part1], Section 3.2. 4>4324 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in [Part1], Section 3.2.6> 4325 4325 <a href="#media.type" class="smpl">type</a> = token 4326 4326 … … 4328 4328 4329 4329 <a href="#quality.values" class="smpl">weight</a> = OWS ";" OWS "q=" qvalue 4330 <a href="#imported.abnf" class="smpl">word</a> = <word, defined in [Part1], Section 3.2. 4>4330 <a href="#imported.abnf" class="smpl">word</a> = <word, defined in [Part1], Section 3.2.6> 4331 4331 4332 4332 <a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT … … 4557 4557 <li><em>Section 5.4</em> <a href="#rfc.xref.Part1.19">6.1</a></li> 4558 4558 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.11">3.1.4.1</a>, <a href="#rfc.xref.Part1.12">3.1.4.2</a>, <a href="#rfc.xref.Part1.27">8</a></li> 4559 <li><em>Section 5.7 </em> <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.44">C</a></li>4559 <li><em>Section 5.7.1</em> <a href="#rfc.xref.Part1.17">5.3.8</a>, <a href="#rfc.xref.Part1.29">8.4.2</a>, <a href="#rfc.xref.Part1.44">C</a></li> 4560 4560 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.35">9.3.1</a></li> 4561 4561 <li><em>Section 6.3</em> <a href="#rfc.xref.Part1.22">7.2.2</a>, <a href="#rfc.xref.Part1.25">7.5.15</a></li>
Note: See TracChangeset
for help on using the changeset viewer.