Changeset 1551 for draft-ietf-httpbis/latest
- Timestamp:
- 28/02/12 08:46:57 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1547 r1551 460 460 } 461 461 @bottom-center { 462 content: "Expires August 24, 2012";462 content: "Expires August 31, 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-02-2 1">509 <meta name="dct.issued" scheme="ISO8601" content="2012-02-28"> 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: August 24, 2012</td>535 <td class="left">Expires: August 31, 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">February 2 1, 2012</td>592 <td class="right">February 28, 2012</td> 593 593 </tr> 594 594 </tbody> … … 620 620 in progress”. 621 621 </p> 622 <p>This Internet-Draft will expire on August 24, 2012.</p>622 <p>This Internet-Draft will expire on August 31, 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> … … 1093 1093 at least one of those representations matches the selected representation. 1094 1094 </p> 1095 <p id="rfc.section.3.2.p.2">If-None-Match MAY also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying1096 an existing representation of the target resource when the client believes that the resource does not have a current representation.1097 Thisis a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation1095 <p id="rfc.section.3.2.p.2">If-None-Match <em class="bcp14">MAY</em> also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying an existing 1096 representation of the target resource when the client believes that the resource does not have a current representation. This 1097 is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation 1098 1098 for the target resource. 1099 1099 </p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1547 r1551 888 888 </t> 889 889 <t> 890 If-None-Match MAYalso be used with a value of "*" to prevent an unsafe890 If-None-Match &MAY; also be used with a value of "*" to prevent an unsafe 891 891 request method (e.g., PUT) from inadvertently modifying an existing 892 892 representation of the target resource when the client believes that -
draft-ietf-httpbis/latest/p6-cache.html
r1547 r1551 463 463 } 464 464 @bottom-center { 465 content: "Expires August 24, 2012";465 content: "Expires August 31, 2012"; 466 466 } 467 467 @bottom-right { … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-02-2 1">513 <meta name="dct.issued" scheme="ISO8601" content="2012-02-28"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <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 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: August 24, 2012</td>539 <td class="left">Expires: August 31, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 602 602 <tr> 603 603 <td class="left"></td> 604 <td class="right">February 2 1, 2012</td>604 <td class="right">February 28, 2012</td> 605 605 </tr> 606 606 </tbody> … … 632 632 in progress”. 633 633 </p> 634 <p>This Internet-Draft will expire on August 24, 2012.</p>634 <p>This Internet-Draft will expire on August 31, 2012.</p> 635 635 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 636 636 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1396 1396 </p> 1397 1397 <ul class="empty"> 1398 <li>The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful1399 validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without1400 contacting it, even by caches that have been configured to returnstale responses.1398 <li>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to 1399 prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return 1400 stale responses. 1401 1401 </li> 1402 1402 <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated -
draft-ietf-httpbis/latest/p6-cache.xml
r1547 r1551 1447 1447 <iref item="no-cache" primary="true" subitem="Cache Directive" /> 1448 1448 <list> 1449 <t>The no-cache response directive indicates that the response MUST NOT1449 <t>The no-cache response directive indicates that the response &MUST-NOT; 1450 1450 be used to satisfy a subsequent request without successful validation on 1451 1451 the origin server. This allows an origin server to prevent a cache from
Note: See TracChangeset
for help on using the changeset viewer.