Changeset 1068 for draft-ietf-httpbis/latest
- Timestamp:
- 28/10/10 07:21:37 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1066 r1068 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-2 7">405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-28"> 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: April 30, 2011</td>436 <td class="left">Expires: May 1, 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 2 7, 2010</td>489 <td class="right">October 28, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on April 30, 2011.</p>516 <p>This Internet-Draft will expire on May 1, 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> … … 1602 1602 <div id="rfc.figure.u.15"></div><pre class="text"> Allow: GET, HEAD, PUT 1603 1603 </pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p> 1604 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other1605 means of communicating with the origin server.1604 <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field -- it does not need to understand all the methods specified in order to handle them according 1605 to the generic message handling rules. 1606 1606 </p> 1607 1607 <div id="rfc.iref.e.1"></div> … … 2674 2674 <ul> 2675 2675 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>>: "205 Bodies" 2676 </li> 2677 <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" 2676 2678 </li> 2677 2679 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/239">http://tools.ietf.org/wg/httpbis/trac/ticket/239</a>>: "Migrate CONNECT from RFC2817 to p2" -
draft-ietf-httpbis/latest/p2-semantics.xml
r1067 r1068 2081 2081 </t> 2082 2082 <t> 2083 A proxy &MUST-NOT; modify the Allow header field even if it does not2084 understand all the methods specified , since the user agent might have other2085 means of communicating with the origin server.2083 A proxy &MUST-NOT; modify the Allow header field -- it does not need to 2084 understand all the methods specified in order to handle them according to 2085 the generic message handling rules. 2086 2086 </t> 2087 2087 </section> … … 3991 3991 </t> 3992 3992 <t> 3993 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/226"/>: 3994 "proxies not supporting certain methods" 3995 </t> 3996 <t> 3993 3997 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/239"/>: 3994 3998 "Migrate CONNECT from RFC2817 to p2"
Note: See TracChangeset
for help on using the changeset viewer.