Changeset 1703 for draft-ietf-httpbis/latest
- Timestamp:
- 03/07/12 07:07:57 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1697 r1703 449 449 } 450 450 @bottom-center { 451 content: "Expires January 2, 2013";451 content: "Expires January 4, 2013"; 452 452 } 453 453 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 1">492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-03"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <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."> … … 516 516 </tr> 517 517 <tr> 518 <td class="left">Expires: January 2, 2013</td>518 <td class="left">Expires: January 4, 2013</td> 519 519 <td class="right">J. Reschke, Editor</td> 520 520 </tr> … … 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">July 1, 2012</td>527 <td class="right">July 3, 2012</td> 528 528 </tr> 529 529 </tbody> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on January 2, 2013.</p>557 <p>This Internet-Draft will expire on January 4, 2013.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 969 969 </li> 970 970 <li>HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will 971 support transparent and efficient caching, and so HTTP/1.1 origin servers still ought to provide Last-Modified values. In 972 those rare cases where the use of a Last-Modified value as a validator by an HTTP/1.0 system could result in a serious problem, 973 then HTTP/1.1 origin servers should not provide one. 971 support transparent and efficient caching, and so HTTP/1.1 origin servers still ought to provide Last-Modified values. 974 972 </li> 975 973 </ul> … … 1350 1348 </li> 1351 1349 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1350 </li> 1351 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/363">http://tools.ietf.org/wg/httpbis/trac/ticket/363</a>>: "Rare cases" 1352 1352 </li> 1353 1353 </ul> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1697 r1703 716 716 last-modified values received or used by these systems will 717 717 support transparent and efficient caching, and so HTTP/1.1 origin 718 servers still ought to provide Last-Modified values. In those rare cases 719 where the use of a Last-Modified value as a validator by an 720 HTTP/1.0 system could result in a serious problem, then HTTP/1.1 721 origin servers should not provide one. 718 servers still ought to provide Last-Modified values. 722 719 </t></list> 723 720 </t> … … 1425 1422 "ABNF requirements for recipients" 1426 1423 </t> 1424 <t> 1425 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/363"/>: 1426 "Rare cases" 1427 </t> 1427 1428 </list> 1428 1429 </t>
Note: See TracChangeset
for help on using the changeset viewer.