Changeset 1097 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 10/12/10 09:00:11 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1095 r1097 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-12- 01">405 <meta name="dct.issued" scheme="ISO8601" content="2010-12-10"> 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: June 4, 2011</td>436 <td class="left">Expires: June 13, 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">December 1 , 2010</td>489 <td class="right">December 10, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on June 4, 2011.</p>516 <p>This Internet-Draft will expire on June 13, 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> … … 1691 1691 <div class="note" id="rfc.section.9.4.p.8"> 1692 1692 <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, 1693 and the Location header field value both contain fragment identifiers. 1693 and the Location header field value both contain fragment identifiers. Thus be aware that including fragment identifiers might 1694 inconvenience anyone relying on the semantics of the original URI's fragment identifier. 1694 1695 </p> 1695 1696 </div> … … 2697 2698 <p id="rfc.section.C.14.p.1">Closed issues: </p> 2698 2699 <ul> 2700 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>>: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect may cause inconvenience 2701 in some cases) 2702 </li> 2699 2703 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>>: "205 Bodies" 2700 2704 </li>
Note: See TracChangeset
for help on using the changeset viewer.