Changeset 1302 for draft-ietf-httpbis/latest
- Timestamp:
- 31/05/11 07:33:19 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1301 r1302 359 359 } 360 360 @bottom-center { 361 content: "Expires November 28, 2011";361 content: "Expires December 2, 2011"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-05- 27">411 <meta name="dct.issued" scheme="ISO8601" content="2011-05-31"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <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 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: November 28, 2011</td>442 <td class="left">Expires: December 2, 2011</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">May 27, 2011</td>495 <td class="right">May 31, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on November 28, 2011.</p>524 <p>This Internet-Draft will expire on December 2, 2011.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.html
r1291 r1302 362 362 } 363 363 @bottom-center { 364 content: "Expires November 28, 2011";364 content: "Expires December 2, 2011"; 365 365 } 366 366 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-05- 27">410 <meta name="dct.issued" scheme="ISO8601" content="2011-05-31"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: November 28, 2011</td>436 <td class="left">Expires: December 2, 2011</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">May 27, 2011</td>497 <td class="right">May 31, 2011</td> 498 498 </tr> 499 499 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on November 28, 2011.</p>525 <p>This Internet-Draft will expire on December 2, 2011.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 770 770 </p> 771 771 <p id="rfc.section.2.1.p.3">In this context, a cache has "understood" a request method or a response status code if it recognises it and implements any 772 cache-specific behavio ur. In particular, 206 Partial Content responses cannot be cached by an implementation that does not772 cache-specific behavior. In particular, 206 Partial Content responses cannot be cached by an implementation that does not 773 773 handle partial content (see <a href="#errors.or.incomplete.response.cache.behavior" title="Storing Partial and Incomplete Responses">Section 2.1.1</a>). 774 774 </p> -
draft-ietf-httpbis/latest/p6-cache.xml
r1292 r1302 488 488 In this context, a cache has "understood" a request method or a response 489 489 status code if it recognises it and implements any cache-specific 490 behavio ur. In particular, 206 Partial Content responses cannot be cached by490 behavior. In particular, 206 Partial Content responses cannot be cached by 491 491 an implementation that does not handle partial content (see <xref 492 492 target="errors.or.incomplete.response.cache.behavior" />).
Note: See TracChangeset
for help on using the changeset viewer.