Changeset 886


Ignore:
Timestamp:
23/07/10 12:40:29 (12 years ago)
Author:
julian.reschke@…
Message:

Note change in [884] relating to issue 199 (see #199)

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

Legend:

Unmodified
Added
Removed

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

    r878 r886  
    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.
     1163      </p>
    11621164      <div id="rfc.iref.28"></div>
    11631165      <div id="rfc.iref.s.5"></div>
    … …  
    11921194         when the response would otherwise be 200 (OK).
    11931195      </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.
     1197      </p>
    11941198      <div id="rfc.iref.31"></div>
    11951199      <div id="rfc.iref.s.8"></div>
    … …  
    11981202         The resource metadata and representation metadata in the response message's header fields refer to the requested resource
    11991203         and its current representation, respectively, after the requested action. For example, if a 204 status is received in response
    1200          to a PUT and the response contains an Etag header field, then the value of that field is the current entity-tag for the representation
     1204         to a PUT and the response contains an ETag header field, then the value of that field is the current entity-tag for the representation
    12011205         that was successfully PUT to the requested resource.
    12021206      </p>
    … …  
    12181222      <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed payload is a partial representation as
    12191223         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>.
     1224      </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.
    12201226      </p>
    12211227      <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>
    … …  
    12391245         upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    12401246      </p>
    1241       <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. This response is cacheable unless indicated otherwise.
     1247      <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.
     1248      </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.
    12421250      </p>
    12431251      <div id="rfc.iref.35"></div>
    … …  
    12451253      <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    12461254      <p id="rfc.section.8.3.2.p.1">The requested resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Effective
    1247          Request URI to one or more of the new references returned by the server, where possible. This response is cacheable unless
    1248          indicated otherwise.
    1249       </p>
    1250       <p id="rfc.section.8.3.2.p.2">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).
    1251       </p>
    1252       <p id="rfc.section.8.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
     1255         Request URI to one or more of the new references returned by the server, where possible.
     1256      </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.
     1258      </p>
     1259      <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).
     1260      </p>
     1261      <p id="rfc.section.8.3.2.p.4">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    12531262         the request was issued.
    12541263      </p>
    1255       <div class="note" id="rfc.section.8.3.2.p.4">
     1264      <div class="note" id="rfc.section.8.3.2.p.5">
    12561265         <p> <b>Note:</b> When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously
    12571266            change it into a GET request.
    … …  
    12621271      <h3 id="rfc.section.8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    12631272      <p id="rfc.section.8.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
    1264          client <em class="bcp14">SHOULD</em> continue to use the Effectice Request URI for future requests. This response is only cacheable if indicated by a Cache-Control
    1265          or Expires header field.
     1273         client <em class="bcp14">SHOULD</em> continue to use the Effective Request URI for future requests.
    12661274      </p>
    12671275      <p id="rfc.section.8.3.3.p.2">The temporary 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).
    … …  
    12941302         description are outside the scope of HTTP and thus entirely determined by the URI owner(s).
    12951303      </p>
    1296       <p id="rfc.section.8.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
    1297          the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
     1304      <p id="rfc.section.8.3.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    12981305      </p>
    12991306      <div id="rfc.iref.38"></div>
    … …  
    13151322      <div id="rfc.iref.s.18"></div>
    13161323      <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    1317       <p id="rfc.section.8.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Effective Request URI for future requests. This response is only cacheable if indicated by a Cache-Control
    1318          or Expires header field.
     1324      <p id="rfc.section.8.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Effective Request URI for future requests.
    13191325      </p>
    13201326      <p id="rfc.section.8.3.8.p.2">The temporary 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) , since many pre-HTTP/1.1 user agents do not understand
    … …  
    14141420      <p id="rfc.section.8.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
    14151421         to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Effective Request URI after user approval. If the server does not know, or has no facility to determine,
    1416          whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
     1422         whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead.
    14171423      </p>
    14181424      <p id="rfc.section.8.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    … …  
    14211427         site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
    14221428         -- that is left to the discretion of the server owner.
     1429      </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.
    14231431      </p>
    14241432      <div id="rfc.iref.53"></div>
    … …  
    14601468      <div id="rfc.iref.s.35"></div>
    14611469      <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
    1462       <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> 
     1470      <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    14631471      </p>
    14641472      <div id="rfc.iref.59"></div>
    … …  
    25922600         </li>
    25932601         <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/199">http://tools.ietf.org/wg/httpbis/trac/ticket/199</a>&gt;: "Status codes and caching"
    25942604         </li>
    25952605      </ul>
    … …  
    28092819                     </ul>
    28102820                  </li>
    2811                   <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="#Part6"><b>13.1</b></a><ul class="ind">
     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>
    28122823                        <li class="indline1"><em>Section 2.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">6.1</a></li>
    28132824                        <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

    r885 r886  
    11841184</t>
    11851185<t>
    1186         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    1187         freshness for 200 responses.
     1186   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1187   freshness for 200 responses.
    11881188</t>
    11891189</section>
    … …  
    12481248</t>
    12491249<t>
    1250         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    1251         freshness for 203 responses.
     1250   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1251   freshness for 203 responses.
    12521252</t>
    12531253
    … …  
    13061306</t>
    13071307<t>
    1308         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    1309         freshness for 206 responses.
     1308   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1309   freshness for 206 responses.
    13101310</t>
    13111311</section>
    … …  
    13581358</t>
    13591359<t>
    1360         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    1361         freshness for 300 responses.
     1360   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1361   freshness for 300 responses.
    13621362</t>
    13631363
    … …  
    13751375</t>
    13761376<t>
    1377         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
    1378         freshness for 301 responses.
     1377   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
     1378   freshness for 301 responses.
    13791379</t>
    13801380<t>
    … …  
    17291729</t>
    17301730<t>
    1731         Caches &MAY; use a heuristic (see &p6-heuristic;) to determine freshness
    1732         for 410 responses.
     1731   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine freshness
     1732   for 410 responses.
    17331733</t>
    17341734
    … …  
    38433843      "Clarify entity / representation / variant terminology"
    38443844    </t>
     3845    <t>
     3846      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/199"/>:
     3847      "Status codes and caching"
     3848    </t>
    38453849  </list>
    38463850</t>
Note: See TracChangeset for help on using the changeset viewer.