Ignore:
Timestamp:
May 20, 2011, 12:06:38 AM (8 years ago)
Author:
julian.reschke@…
Message:

editorial: remove tabs, tune markup, regen HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r1284 r1287  
    837837         with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>.
    838838      </p>
    839       <p id="rfc.section.2.3.p.8"> <span class="comment" id="ISSUE-no-req-for-directives">[<a href="#ISSUE-no-req-for-directives" class="smpl">ISSUE-no-req-for-directives</a>: there are not requirements directly applying to cache-request-directives and freshness.]</span>
    840       </p>
    841       <p id="rfc.section.2.3.p.9">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
     839      <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
    842840         a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;4</a> for an explanation of the difference between caches and history mechanisms.
    843841      </p>
     
    12661264         it will also see and understand the private directive and thus default to the safe behavior.
    12671265      </p>
    1268       <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> be ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
     1266      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
    12691267         will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
    12701268         minimally correct even if the cache does not understand the extension(s).
     
    13241322Cache-Control: max-age=30
    13251323Pragma: no-cache
     1324
    13261325</pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
    13271326         understand Cache-Control from serving a cached response.
    13281327      </p>
    13291328      <div class="note" id="rfc.section.3.4.p.8">
    1330          <p>Note: Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement
    1331             for "Cache-Control: no-cache" in them.
     1329         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
     1330            no-cache" in them.
    13321331         </p>
    13331332      </div>
Note: See TracChangeset for help on using the changeset viewer.