* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1703


Ignore:
Timestamp:
2012-07-03 00:07:57 (2 years ago)
Author:
julian.reschke@gmx.de
Message:

Remove mention of "rare cases" with respect to HTTP/1.0 (see #363)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.html

    r1697 r1703  
    449449  }  
    450450  @bottom-center { 
    451        content: "Expires January 2, 2013";  
     451       content: "Expires January 4, 2013";  
    452452  }  
    453453  @bottom-right { 
     
    490490      <meta name="dct.creator" content="Reschke, J. F."> 
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 
    492       <meta name="dct.issued" scheme="ISO8601" content="2012-07-01"> 
     492      <meta name="dct.issued" scheme="ISO8601" content="2012-07-03"> 
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    494494      <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 &#34;HTTP/1.1&#34; 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."> 
     
    516516            </tr> 
    517517            <tr> 
    518                <td class="left">Expires: January 2, 2013</td> 
     518               <td class="left">Expires: January 4, 2013</td> 
    519519               <td class="right">J. Reschke, Editor</td> 
    520520            </tr> 
     
    525525            <tr> 
    526526               <td class="left"></td> 
    527                <td class="right">July 1, 2012</td> 
     527               <td class="right">July 3, 2012</td> 
    528528            </tr> 
    529529         </tbody> 
     
    555555         in progress”. 
    556556      </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> 
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    969969         </li> 
    970970         <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. 
    974972         </li> 
    975973      </ul> 
     
    13501348         </li> 
    13511349         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients" 
     1350         </li> 
     1351         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/363">http://tools.ietf.org/wg/httpbis/trac/ticket/363</a>&gt;: "Rare cases" 
    13521352         </li> 
    13531353      </ul> 
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1697 r1703  
    716716      last-modified values received or used by these systems will 
    717717      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. 
    722719  </t></list> 
    723720</t> 
     
    14251422      "ABNF requirements for recipients" 
    14261423    </t> 
     1424    <t> 
     1425      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/363"/>: 
     1426      "Rare cases" 
     1427    </t> 
    14271428  </list> 
    14281429</t> 
Note: See TracChangeset for help on using the changeset viewer.