Changeset 1283 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 19/05/11 08:43:51 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1276 r1283 359 359 } 360 360 @bottom-center { 361 content: "Expires November 2 , 2011";361 content: "Expires November 20, 2011"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-05- 01">411 <meta name="dct.issued" scheme="ISO8601" content="2011-05-19"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <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."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: November 2 , 2011</td>442 <td class="left">Expires: November 20, 2011</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">May 1 , 2011</td>495 <td class="right">May 19, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on November 2 , 2011.</p>524 <p>This Internet-Draft will expire on November 20, 2011.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2032 2032 <p>Examples are:</p> <pre class="text"> Location: http://www.example.org/pub/WWW/People.html#tim 2033 2033 </pre><div id="rfc.figure.u.15"></div><pre class="text"> Location: /index.html 2034 </pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p> 2035 <ul> 2036 <li>With a 201 Created response, because in this usage the Location header field specifies the URI for the entire created resource.</li> 2037 <li>With 305 Use Proxy.</li> 2038 </ul> 2034 </pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears 2035 in a 201 Created response, where the Location header field specifies the URI for the entire created resource. 2036 </p> 2039 2037 <div class="note" id="rfc.section.9.4.p.8"> 2040 2038 <p> <b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to by the user agent,
Note: See TracChangeset
for help on using the changeset viewer.