28/02/09 19:39:48 (13 years ago)

make indentation of examples consistent

1 edited


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

    r454 r458  
    982982         than the one for the existing entry, then the client <em class="bcp14">SHOULD</em> repeat the request unconditionally, and include
    983983      </p>
    984       <div id="rfc.figure.u.9"></div><pre class="text">    Cache-Control: max-age=0
     984      <div id="rfc.figure.u.9"></div><pre class="text">  Cache-Control: max-age=0
    985985</pre><p id="rfc.section.3.6.p.5">to force any intermediate caches to validate their copies directly with the origin server, or</p>
    986       <div id="rfc.figure.u.10"></div><pre class="text">    Cache-Control: no-cache
     986      <div id="rfc.figure.u.10"></div><pre class="text">  Cache-Control: no-cache
    987987</pre><p id="rfc.section.3.6.p.7">to force any intermediate caches to obtain a new copy from the origin server.</p>
    988988      <p id="rfc.section.3.6.p.8">If the Date values are equal, then the client <em class="bcp14">MAY</em> use either response (or <em class="bcp14">MAY</em>, if it is being extremely prudent, request a new response). Servers <em class="bcp14">MUST NOT</em> depend on clients being able to choose deterministically between responses generated during the same second, if their expiration
    15591559         an otherwise private response in their shared cache(s) could do so by including
    15601560      </p>
    1561       <div id="rfc.figure.u.14"></div><pre class="text">    Cache-Control: private, community="UCI"
     1561      <div id="rfc.figure.u.14"></div><pre class="text">  Cache-Control: private, community="UCI"
    15621562</pre><p id="rfc.section.15.2.6.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
    15631563         it will also see and understand the private directive and thus default to the safe behavior.
Note: See TracChangeset for help on using the changeset viewer.