Changeset 1070 for draft-ietf-httpbis
- Timestamp:
- 30/10/10 16:38:30 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1068 r1070 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-10- 28">405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-30"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: May 1, 2011</td>436 <td class="left">Expires: May 3, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">October 28, 2010</td>489 <td class="right">October 30, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on May 1, 2011.</p>516 <p>This Internet-Draft will expire on May 3, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1695 1695 <p id="rfc.section.9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1). 1696 1696 </p> 1697 <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly 1698 referred to as part of that method definition. 1697 <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods. 1699 1698 </p> 1700 1699 <div id="rfc.iref.r.1"></div> … … 2354 2353 (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section 9.4</a>) 2355 2354 </p> 2356 <p id="rfc.section.A.p.8">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.6</a>) 2357 </p> 2358 <p id="rfc.section.A.p.9">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 2355 <p id="rfc.section.A.p.8">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 9.5</a>) 2356 </p> 2357 <p id="rfc.section.A.p.9">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 9.6</a>) 2358 </p> 2359 <p id="rfc.section.A.p.10">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated 2359 2360 correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 9.8</a>) 2360 2361 </p> … … 2674 2675 <ul> 2675 2676 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>>: "205 Bodies" 2677 </li> 2678 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/203">http://tools.ietf.org/wg/httpbis/trac/ticket/203</a>>: "Max-Forwards vs extension methods" 2676 2679 </li> 2677 2680 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/226">http://tools.ietf.org/wg/httpbis/trac/ticket/226</a>>: "proxies not supporting certain methods" … … 2806 2809 <li class="indline1">From <a class="iref" href="#rfc.xref.header.from.1">3</a>, <a class="iref" href="#rfc.iref.h.4"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.header.from.2">10.3</a></li> 2807 2810 <li class="indline1">Location <a class="iref" href="#rfc.xref.header.location.1">5</a>, <a class="iref" href="#rfc.xref.header.location.2">7.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>9.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">10.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A</a></li> 2808 <li class="indline1">Max-Forwards <a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.2</a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">7.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.4">10.3</a> </li>2811 <li class="indline1">Max-Forwards <a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.2</a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">7.8</a>, <a class="iref" href="#rfc.iref.h.6"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.4">10.3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.5">A</a></li> 2809 2812 <li class="indline1">Referer <a class="iref" href="#rfc.xref.header.referer.1">3</a>, <a class="iref" href="#rfc.iref.h.7"><b>9.6</b></a>, <a class="iref" href="#rfc.xref.header.referer.2">10.3</a>, <a class="iref" href="#rfc.xref.header.referer.3">A</a></li> 2810 2813 <li class="indline1">Retry-After <a class="iref" href="#rfc.xref.header.retry-after.1">5</a>, <a class="iref" href="#rfc.iref.h.8"><b>9.7</b></a>, <a class="iref" href="#rfc.xref.header.retry-after.2">10.3</a></li> … … 2824 2827 </li> 2825 2828 <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind"> 2826 <li class="indline1">Max-Forwards header <a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.2</a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">7.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.4">10.3</a> </li>2829 <li class="indline1">Max-Forwards header <a class="iref" href="#rfc.xref.header.max-forwards.1">3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.2">7.2</a>, <a class="iref" href="#rfc.xref.header.max-forwards.3">7.8</a>, <a class="iref" href="#rfc.iref.m.9"><b>9.5</b></a>, <a class="iref" href="#rfc.xref.header.max-forwards.4">10.3</a>, <a class="iref" href="#rfc.xref.header.max-forwards.5">A</a></li> 2827 2830 <li class="indline1">Methods 2828 2831 <ul class="ind"> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1068 r1070 2282 2282 </t> 2283 2283 <t> 2284 The Max-Forwards header field &MAY; be ignored for all other methods 2285 defined by this specification and for any extension methods for which 2286 it is not explicitly referred to as part of that method definition. 2284 The Max-Forwards header field &MAY; be ignored for all other methods. 2287 2285 </t> 2288 2286 </section> … … 3464 3462 </t> 3465 3463 <t> 3464 Restrict Max-Forwards header field to OPTIONS and TRACE (previously, 3465 extension methods could have used it as well). 3466 (<xref target="header.max-forwards"/>) 3467 </t> 3468 <t> 3466 3469 Allow Referer field value of "about:blank" as alternative to not specifying it. 3467 3470 (<xref target="header.referer"/>) … … 3991 3994 </t> 3992 3995 <t> 3996 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/203"/>: 3997 "Max-Forwards vs extension methods" 3998 </t> 3999 <t> 3993 4000 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/226"/>: 3994 4001 "proxies not supporting certain methods"
Note: See TracChangeset
for help on using the changeset viewer.