Changeset 889


Ignore:
Timestamp:
23/07/10 14:53:02 (12 years ago)
Author:
julian.reschke@…
Message:

Note change in [888] relating to issue 139 (see #139)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p2-semantics.html

    r886 r889  
    10071007         be completed without transferring data already held by the client.
    10081008      </p>
    1009       <p id="rfc.section.7.3.p.5">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1009      <p id="rfc.section.7.3.p.5">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    10101010      </p>
    10111011      <p id="rfc.section.7.3.p.6">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
    … …  
    10181018         hypertext links for validity, accessibility, and recent modification.
    10191019      </p>
    1020       <p id="rfc.section.7.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource. If the new field values indicate that the cached
     1020      <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached
    10211021         representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5,
    10221022         ETag or Last-Modified), then the cache <em class="bcp14">MUST</em> treat the cache entry as stale.
    … …  
    10451045         a Location header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
    10461046      </p>
    1047       <p id="rfc.section.7.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
    1048          However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
     1047      <p id="rfc.section.7.5.p.5">Responses to POST requests are cacheable only when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). Such cached POST responses <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests. Note that POST caching is not widely implemented. However, the 303 (See
     1048         Other) response can be used to direct the user agent to retrieve a cacheable resource.
    10491049      </p>
    10501050      <div id="rfc.iref.p.2"></div>
    … …  
    10891089      </p>
    10901090      <p id="rfc.section.7.7.p.3">If the request passes through a cache and the Effective Request URI identifies one or more currently cached representations,
    1091          those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to the DELETE method <em class="bcp14">MUST NOT</em> be cached.
     1091         those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to the DELETE method are not cacheable.
    10921092      </p>
    10931093      <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    … …  
    11031103         infinite loop.
    11041104      </p>
    1105       <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method <em class="bcp14">MUST NOT</em> be cached.
     1105      <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    11061106      </p>
    11071107      <div id="rfc.iref.c.1"></div>
    … …  
    11601160         <dd>a representation containing the request message as received by the end server.</dd>
    11611161      </dl>
    1162       <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     1162      <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    11631163      </p>
    11641164      <div id="rfc.iref.28"></div>
    … …  
    11941194         when the response would otherwise be 200 (OK).
    11951195      </p>
    1196       <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     1196      <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    11971197      </p>
    11981198      <div id="rfc.iref.31"></div>
    … …  
    12231223         defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.11"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    12241224      </p>
    1225       <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.
     1225      <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.
    12261226      </p>
    12271227      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    … …  
    12471247      <p id="rfc.section.8.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    12481248      </p>
    1249       <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     1249      <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    12501250      </p>
    12511251      <div id="rfc.iref.35"></div>
    … …  
    12551255         Request URI to one or more of the new references returned by the server, where possible.
    12561256      </p>
    1257       <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     1257      <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    12581258      </p>
    12591259      <p id="rfc.section.8.3.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    … …  
    14281428         -- that is left to the discretion of the server owner.
    14291429      </p>
    1430       <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     1430      <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    14311431      </p>
    14321432      <div id="rfc.iref.53"></div>
    … …  
    26002600         </li>
    26012601         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
     2602         </li>
     2603         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/139">http://tools.ietf.org/wg/httpbis/trac/ticket/139</a>&gt;: "Methods and Caching"
    26022604         </li>
    26032605         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>&gt;: "Status codes and caching"
    … …  
    28192821                     </ul>
    28202822                  </li>
    2821                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.3">5</a>, <a class="iref" href="#rfc.xref.Part6.4">5</a>, <a class="iref" href="#rfc.xref.Part6.5">6.1</a>, <a class="iref" href="#rfc.xref.Part6.6">7.3</a>, <a class="iref" href="#rfc.xref.Part6.7">8.2.1</a>, <a class="iref" href="#rfc.xref.Part6.8">8.2.4</a>, <a class="iref" href="#rfc.xref.Part6.9">8.2.7</a>, <a class="iref" href="#rfc.xref.Part6.10">8.3.1</a>, <a class="iref" href="#rfc.xref.Part6.11">8.3.2</a>, <a class="iref" href="#rfc.xref.Part6.12">8.4.11</a>, <a class="iref" href="#Part6"><b>13.1</b></a><ul class="ind">
    2822                         <li class="indline1"><em>Section 2.3.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.7">8.2.1</a>, <a class="iref" href="#rfc.xref.Part6.8">8.2.4</a>, <a class="iref" href="#rfc.xref.Part6.9">8.2.7</a>, <a class="iref" href="#rfc.xref.Part6.10">8.3.1</a>, <a class="iref" href="#rfc.xref.Part6.11">8.3.2</a>, <a class="iref" href="#rfc.xref.Part6.12">8.4.11</a></li>
     2823                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.3">5</a>, <a class="iref" href="#rfc.xref.Part6.4">5</a>, <a class="iref" href="#rfc.xref.Part6.5">6.1</a>, <a class="iref" href="#rfc.xref.Part6.6">7.3</a>, <a class="iref" href="#rfc.xref.Part6.7">7.4</a>, <a class="iref" href="#rfc.xref.Part6.8">7.5</a>, <a class="iref" href="#rfc.xref.Part6.9">8.2.1</a>, <a class="iref" href="#rfc.xref.Part6.10">8.2.4</a>, <a class="iref" href="#rfc.xref.Part6.11">8.2.7</a>, <a class="iref" href="#rfc.xref.Part6.12">8.3.1</a>, <a class="iref" href="#rfc.xref.Part6.13">8.3.2</a>, <a class="iref" href="#rfc.xref.Part6.14">8.4.11</a>, <a class="iref" href="#Part6"><b>13.1</b></a><ul class="ind">
     2824                        <li class="indline1"><em>Section 2.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.8">7.5</a></li>
     2825                        <li class="indline1"><em>Section 2.3.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.9">8.2.1</a>, <a class="iref" href="#rfc.xref.Part6.10">8.2.4</a>, <a class="iref" href="#rfc.xref.Part6.11">8.2.7</a>, <a class="iref" href="#rfc.xref.Part6.12">8.3.1</a>, <a class="iref" href="#rfc.xref.Part6.13">8.3.2</a>, <a class="iref" href="#rfc.xref.Part6.14">8.4.11</a></li>
    28232826                        <li class="indline1"><em>Section 2.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">6.1</a></li>
    28242827                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part6.3">5</a></li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r888 r889  
    38503850    </t>
    38513851    <t>
     3852      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/139"/>:
     3853      "Methods and Caching"
     3854    </t>
     3855    <t>
    38523856      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/199"/>:
    38533857      "Status codes and caching"
Note: See TracChangeset for help on using the changeset viewer.