Changeset 1604 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 21/03/12 12:30:28 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1592 r1604 460 460 } 461 461 @bottom-center { 462 content: "Expires September 13, 2012";462 content: "Expires September 22, 2012"; 463 463 } 464 464 @bottom-right { … … 501 501 <meta name="dct.creator" content="Reschke, J. F."> 502 502 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 503 <meta name="dct.issued" scheme="ISO8601" content="2012-03- 12">503 <meta name="dct.issued" scheme="ISO8601" content="2012-03-21"> 504 504 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 505 505 <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."> … … 527 527 </tr> 528 528 <tr> 529 <td class="left">Expires: September 13, 2012</td>529 <td class="left">Expires: September 22, 2012</td> 530 530 <td class="right">J. Reschke, Editor</td> 531 531 </tr> … … 536 536 <tr> 537 537 <td class="left"></td> 538 <td class="right">March 12, 2012</td>538 <td class="right">March 21, 2012</td> 539 539 </tr> 540 540 </tbody> … … 566 566 in progress”. 567 567 </p> 568 <p>This Internet-Draft will expire on September 13, 2012.</p>568 <p>This Internet-Draft will expire on September 22, 2012.</p> 569 569 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 570 570 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 948 948 949 949 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7"> 950 <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation mustbe distinct950 <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct 951 951 from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings 952 952 (<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.
Note: See TracChangeset
for help on using the changeset viewer.