26/08/11 14:51:22 (9 years ago)

consistent anchors (does not affect actual spec text)

1 edited


  • draft-ietf-httpbis/latest/p6-cache.html

    r1408 r1415  
    362362  }
    363363  @bottom-center {
    364        content: "Expires February 25, 2012";
     364       content: "Expires February 27, 2012";
    365365  }
    366366  @bottom-right {
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-08-24">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-08-26">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <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 &#34;HTTP/1.1&#34; 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.">
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: February 25, 2012</td>
     436               <td class="left">Expires: February 27, 2012</td>
    437437               <td class="right">J. Mogul</td>
    438438            </tr>
    495495            <tr>
    496496               <td class="left"></td>
    497                <td class="right">August 24, 2011</td>
     497               <td class="right">August 26, 2011</td>
    498498            </tr>
    499499         </tbody>
    525525         in progress”.
    526526      </p>
    527       <p>This Internet-Draft will expire on February 25, 2012.</p>
     527      <p>This Internet-Draft will expire on February 27, 2012.</p>
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    575575            </ul>
    576576         </li>
    577          <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     577         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
    578578               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    579579               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
    11101110         </li>
    11111111      </ul>
    1112       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
     1112      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
    11131113      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to caching.</p>
    11141114      <div id="rfc.iref.a.2"></div>
    17831783      <p id="rfc.section.A.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
    17841784      </p>
    1785       <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;3</a>)
     1785      <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;3</a>)
    17861786      </p>
    17871787      <p id="rfc.section.A.p.5">Do not mention RFC 2047 encoding and multiple languages in Warning header fields anymore, as these aspects never were implemented.
Note: See TracChangeset for help on using the changeset viewer.