Ignore:
Timestamp:
Mar 10, 2011, 10:45:43 PM (9 years ago)
Author:
fielding@…
Message:

update generated HTML

File:
1 edited

Legend:

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

    r1162 r1164  
    783783         </li>
    784784         <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
    785          <li>selecting request-header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
     785         <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>), and
    786786         </li>
    787787         <li>the presented request and stored response are free from directives that would prevent its use (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section&nbsp;3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section&nbsp;3.4</a>), and
     
    868868      </div>
    869869      <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a id="age.calculations" href="#age.calculations">Calculating Age</a></h3>
    870       <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age response-header field to convey the estimated age of the response message when obtained from a cache.
    871          The Age field value is the cache's estimate of the amount of time since the response was generated or validated by the origin
    872          server. In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the
    873          path from the origin server, plus the amount of time it has been in transit along network paths.
     870      <p id="rfc.section.2.3.2.p.1">HTTP/1.1 uses the Age header field to convey the estimated age of the response message when obtained from a cache. The Age
     871         field value is the cache's estimate of the amount of time since the response was generated or validated by the origin server.
     872         In essence, the Age value is the sum of the time that the response has been resident in each of the caches along the path
     873         from the origin server, plus the amount of time it has been in transit along network paths.
    874874      </p>
    875875      <p id="rfc.section.2.3.2.p.2">The following data is used for the age calculation:</p>
     
    990990      </p>
    991991      <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2>
    992       <p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has a Vary header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;3.5</a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting request-header fields nominated by the Vary header field match in both the original
     992      <p id="rfc.section.2.7.p.1">When a cache receives a request that can be satisfied by a stored response that has a Vary header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;3.5</a>), it <em class="bcp14">MUST NOT</em> use that response unless all of the selecting header fields nominated by the Vary header field match in both the original
    993993         request (i.e., that associated with the stored response), and the presented request.
    994994      </p>
    995       <p id="rfc.section.2.7.p.2">The selecting request-header fields from two requests are defined to match if and only if those in the first request can be
    996          transformed to those in the second request by applying any of the following:
     995      <p id="rfc.section.2.7.p.2">The selecting header fields from two requests are defined to match if and only if those in the first request can be transformed
     996         to those in the second request by applying any of the following:
    997997      </p>
    998998      <ul>
    999999         <li>adding or removing whitespace, where allowed in the header field's syntax</li>
    1000          <li>combining multiple message-header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
     1000         <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>)
    10011001         </li>
    10021002         <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
     
    10101010         by the origin server.
    10111011      </p>
    1012       <p id="rfc.section.2.7.p.5">The stored response with matching selecting request-header fields is known as the selected response.</p>
     1012      <p id="rfc.section.2.7.p.5">The stored response with matching selecting header fields is known as the selected response.</p>
    10131013      <p id="rfc.section.2.7.p.6">If no selected response is available, the cache <em class="bcp14">MAY</em> forward the presented request to the origin server in a conditional request; see <a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>.
    10141014      </p>
     
    10401040      <div id="rfc.iref.h.2"></div>
    10411041      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.age" href="#header.age">Age</a></h2>
    1042       <p id="rfc.section.3.1.p.1">The "Age" response-header field conveys the sender's estimate of the amount of time since the response was generated or successfully
     1042      <p id="rfc.section.3.1.p.1">The "Age" header field conveys the sender's estimate of the amount of time since the response was generated or successfully
    10431043         validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>.
    10441044      </p>
     
    10581058      <div id="rfc.iref.h.3"></div>
    10591059      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2>
    1060       <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives for caches along the request/response chain. Such cache
    1061          directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to
    1062          be given in the response.
     1060      <p id="rfc.section.3.2.p.1">The "Cache-Control" header field is used to specify directives for caches along the request/response chain. Such cache directives
     1061         are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given
     1062         in the response.
    10631063      </p>
    10641064      <p id="rfc.section.3.2.p.2">A cache <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled.
     
    13031303      <div id="rfc.iref.h.5"></div>
    13041304      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.pragma" href="#header.pragma">Pragma</a></h2>
    1305       <p id="rfc.section.3.4.p.1">The "Pragma" general-header field is used to include implementation-specific directives that might apply to any recipient
    1306          along the request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however,
    1307          some systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
     1305      <p id="rfc.section.3.4.p.1">The "Pragma" header field is used to include implementation-specific directives that might apply to any recipient along the
     1306         request/response chain. All pragma directives specify optional behavior from the viewpoint of the protocol; however, some
     1307         systems <em class="bcp14">MAY</em> require that behavior be consistent with the directives.
    13081308      </p>
    13091309      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.pragma" class="smpl">Pragma</a>            = "Pragma" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.pragma" class="smpl">Pragma-v</a>
     
    13151315      </p>
    13161316      <div class="note" id="rfc.section.3.4.p.4">
    1317          <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable
    1318             replacement for "Cache-Control: no-cache" in a response.
     1317         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" as a header field is not actually specified, it does not provide a reliable replacement
     1318            for "Cache-Control: no-cache" in a response.
    13191319         </p>
    13201320      </div>
     
    13231323      <div id="rfc.iref.h.6"></div>
    13241324      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h2>
    1325       <p id="rfc.section.3.5.p.1">The "Vary" response-header field conveys the set of request-header fields that were used to select the representation.</p>
     1325      <p id="rfc.section.3.5.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
    13261326      <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request
    13271327         without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section&nbsp;2.7</a>.
     
    13321332      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span>  <a href="#header.vary" class="smpl">Vary</a>   = "Vary" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.vary" class="smpl">Vary-v</a>
    13331333  <a href="#header.vary" class="smpl">Vary-v</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
    1334 </pre><p id="rfc.section.3.5.p.5">The set of header fields named by the Vary field value is known as the selecting request-header fields.</p>
     1334</pre><p id="rfc.section.3.5.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
    13351335      <p id="rfc.section.3.5.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to server-driven negotiation. Doing so allows a cache
    13361336         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
     
    13381338         the user agent with useful information about the dimensions over which the response varies at the time of the response.
    13391339      </p>
    1340       <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the request-header fields (e.g., the network
    1341          address of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether
    1342          this response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
    1343       </p>
    1344       <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard request-header fields defined by this specification. Field names
    1345          are case-insensitive.
     1340      <p id="rfc.section.3.5.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
     1341         of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
     1342         response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
     1343      </p>
     1344      <p id="rfc.section.3.5.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     1345         case-insensitive.
    13461346      </p>
    13471347      <div id="rfc.iref.w.1"></div>
    13481348      <div id="rfc.iref.h.7"></div>
    13491349      <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="header.warning" href="#header.warning">Warning</a></h2>
    1350       <p id="rfc.section.3.6.p.1">The "Warning" general-header field is used to carry additional information about the status or transformation of a message
    1351          that might not be reflected in the message. This information is typically used to warn about possible incorrectness introduced
    1352          by caching operations or transformations applied to the payload of the message.
     1350      <p id="rfc.section.3.6.p.1">The "Warning" header field is used to carry additional information about the status or transformation of a message that might
     1351         not be reflected in the message. This information is typically used to warn about possible incorrectness introduced by caching
     1352         operations or transformations applied to the payload of the message.
    13531353      </p>
    13541354      <p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status
Note: See TracChangeset for help on using the changeset viewer.