Changeset 960
- Timestamp:
- 28/07/10 08:36:00 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r957 r960 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-2 7">402 <meta name="dct.issued" scheme="ISO8601" content="2010-07-28"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <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 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."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: January 2 8, 2011</td>428 <td class="left">Expires: January 29, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">July 2 7, 2010</td>485 <td class="right">July 28, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire in January 2 8, 2011.</p>511 <p>This Internet-Draft will expire in January 29, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 693 693 </p> 694 694 <p id="rfc.section.3.1.p.4">If a 304 response includes an entity-tag that indicates a representation not currently cached, then the recipient <em class="bcp14">MUST NOT</em> use the 304 to update its own cache. If that conditional request originated with an outbound client, such as a user agent 695 with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">M UST</em> be forwarded to the outbound client. Otherwise, disregard the response and repeat the request without the conditional.695 with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">MAY</em> be forwarded to the outbound client. Otherwise, disregard the response and repeat the request without the conditional. 696 696 </p> 697 697 <p id="rfc.section.3.1.p.5">If a cache uses a received 304 response to update a cache entry, the cache <em class="bcp14">MUST</em> update the entry to reflect any new field values given in the response. -
draft-ietf-httpbis/latest/p4-conditional.xml
r925 r960 429 429 use the 304 to update its own cache. If that conditional request originated 430 430 with an outbound client, such as a user agent with its own cache sending a 431 conditional GET to a shared proxy, then the 304 response &M UST; be431 conditional GET to a shared proxy, then the 304 response &MAY; be 432 432 forwarded to the outbound client. Otherwise, disregard the response 433 433 and repeat the request without the conditional.
Note: See TracChangeset
for help on using the changeset viewer.