Changeset 2227 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 25/04/13 14:25:26 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2223 r2227 449 449 } 450 450 @bottom-center { 451 content: "Expires October 2 1, 2013";451 content: "Expires October 27, 2013"; 452 452 } 453 453 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-04- 19">496 <meta name="dct.issued" scheme="ISO8601" content="2013-04-25"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <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."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">April 19, 2013</td>524 <td class="right">April 25, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: October 2 1, 2013</td>527 <td class="left">Expires: October 27, 2013</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on October 2 1, 2013.</p>555 <p>This Internet-Draft will expire on October 27, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 3618 3618 </li> 3619 3619 <li> 3620 <p>Whether the field should be stored by origin servers that understand it upon a PUT request.</p> 3621 </li> 3622 <li> 3620 3623 <p>Whether the field semantics are further refined by the context, such as by existing request methods or status codes.</p> 3621 3624 </li> … … 3628 3631 </li> 3629 3632 <li> 3630 <p> How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).3633 <p>That when the header is used in requests and affects response selection (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), it ought to be listed in the <a href="#header.vary" class="smpl">Vary</a> response header field (<a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section 7.1.4</a>). 3631 3634 </p> 3632 3635 </li> … … 3790 3793 <td class="left">http</td> 3791 3794 <td class="left">standard</td> 3792 <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary. 3" title="Vary">Section 7.1.4</a>3795 <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section 7.1.4</a> 3793 3796 </td> 3794 3797 </tr> … … 4720 4723 <li><em>Section 4.1.1</em> <a href="#rfc.xref.Part6.5">4.3.3</a></li> 4721 4724 <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a></li> 4722 <li><em>Section 4.3</em> <a href="#rfc.xref.Part6.26">7.1.4</a> </li>4725 <li><em>Section 4.3</em> <a href="#rfc.xref.Part6.26">7.1.4</a>, <a href="#rfc.xref.Part6.29">8.3.1</a></li> 4723 4726 <li><em>Section 5</em> <a href="#rfc.xref.Part6.4">4.3.2</a></li> 4724 4727 <li><em>Section 6</em> <a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a></li> … … 4851 4854 </li> 4852 4855 <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul> 4853 <li>Vary header field <a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3. 2</a></li>4856 <li>Vary header field <a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3.1</a>, <a href="#rfc.xref.header.vary.4">8.3.2</a></li> 4854 4857 </ul> 4855 4858 </li>
Note: See TracChangeset
for help on using the changeset viewer.