Changeset 1580 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 11/03/12 05:43:44 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1569 r1580 460 460 } 461 461 @bottom-center { 462 content: "Expires September 9, 2012";462 content: "Expires September 11, 2012"; 463 463 } 464 464 @bottom-right { … … 507 507 <meta name="dct.creator" content="Reschke, J. F."> 508 508 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 509 <meta name="dct.issued" scheme="ISO8601" content="2012-03- 08">509 <meta name="dct.issued" scheme="ISO8601" content="2012-03-10"> 510 510 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 511 511 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 533 533 </tr> 534 534 <tr> 535 <td class="left">Expires: September 9, 2012</td>535 <td class="left">Expires: September 11, 2012</td> 536 536 <td class="right">J. Mogul</td> 537 537 </tr> … … 590 590 <tr> 591 591 <td class="left"></td> 592 <td class="right">March 8, 2012</td>592 <td class="right">March 10, 2012</td> 593 593 </tr> 594 594 </tbody> … … 620 620 in progress”. 621 621 </p> 622 <p>This Internet-Draft will expire on September 9, 2012.</p>622 <p>This Internet-Draft will expire on September 11, 2012.</p> 623 623 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 624 624 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1003 1003 <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct 1004 1004 from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings 1005 (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 5</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.1005 (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags. 1006 1006 </p> 1007 1007 </div> … … 1630 1630 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.4">1.2</a></li> 1631 1631 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.5">1.2</a></li> 1632 <li><em>Section 5</em> <a href="#rfc.xref.Part1.6">2.3.3</a></li>1632 <li><em>Section 4</em> <a href="#rfc.xref.Part1.6">2.3.3</a></li> 1633 1633 <li><em>Section 11</em> <a href="#rfc.xref.Part1.8">7</a></li> 1634 1634 </ul>
Note: See TracChangeset
for help on using the changeset viewer.