Ignore:
Timestamp:
02/09/11 02:32:32 (12 years ago)
Author:
mnot@…
Message:

Turn non-requirement SHOULDs and MAYs into prose; strengthen some obvious candidates into MUST, as per discussion. See #313

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p5-range.html

    r1426 r1433  
    359359  }
    360360  @bottom-center {
    361        content: "Expires March 4, 2012";
     361       content: "Expires March 5, 2012";
    362362  }
    363363  @bottom-right {
    … …  
    406406      <meta name="dct.creator" content="Reschke, J. F.">
    407407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    408       <meta name="dct.issued" scheme="ISO8601" content="2011-09-01">
     408      <meta name="dct.issued" scheme="ISO8601" content="2011-09-02">
    409409      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    410410      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
    … …  
    432432            </tr>
    433433            <tr>
    434                <td class="left">Expires: March 4, 2012</td>
     434               <td class="left">Expires: March 5, 2012</td>
    435435               <td class="right">J. Mogul</td>
    436436            </tr>
    … …  
    489489            <tr>
    490490               <td class="left"></td>
    491                <td class="right">September 1, 2011</td>
     491               <td class="right">September 2, 2011</td>
    492492            </tr>
    493493         </tbody>
    … …  
    517517         in progress”.
    518518      </p>
    519       <p>This Internet-Draft will expire on March 4, 2012.</p>
     519      <p>This Internet-Draft will expire on March 5, 2012.</p>
    520520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    521521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

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

    r1426 r1433  
    473473   positive integer it can represent, or if any of its subsequent calculations
    474474   overflows, it &MUST; consider the value to be 2147483648 (2<x:sup>31</x:sup>).
    475    Recipients parsing a delta-seconds value &SHOULD; use an arithmetic type of
     475   Recipients parsing a delta-seconds value &MUST; use an arithmetic type of
    476476   at least 31 bits of range, and senders &MUST-NOT; send delta-seconds with a
    477477   value greater than 2147483648.
    … …  
    751751</t>
    752752<t>
    753    Also, if the response has a Last-Modified header field (&header-last-modified;),
    754    a cache &SHOULD-NOT; use a heuristic expiration value that is more than some
    755    fraction of the interval since that time. A typical setting of this fraction
    756    might be 10%.
     753   Also, if the response has a Last-Modified header field
     754   (&header-last-modified;), caches are encouraged to use a heuristic
     755   expiration value that is no more than some fraction of the interval since
     756   that time. A typical setting of this fraction might be 10%.
    757757</t>
    758758<x:note>
    … …  
    911911</t>
    912912<t>
    913    A cache &SHOULD-NOT; return stale responses unless it is disconnected
     913   A cache &MUST-NOT; return stale responses unless it is disconnected
    914914   (i.e., it cannot contact the origin server or otherwise find a forward
    915915   path) or doing so is explicitly allowed (e.g., by the max-stale request
    … …  
    926926   304 (Not Modified) response) that it would normally forward to the
    927927   requesting client, and the received response is no longer fresh, the cache
    928    &SHOULD; forward it to the requesting client without adding a new Warning
    929    (but without removing any existing Warning header fields). A cache &SHOULD-NOT;
     928   can forward it to the requesting client without adding a new Warning (but
     929   without removing any existing Warning header fields). A cache shouldn't
    930930   attempt to validate a response simply because that response became stale in
    931931   transit.
    … …  
    945945</t>
    946946<t>
    947    When sending such a conditional request, a cache &SHOULD; add an
    948    If-Modified-Since header field whose value is that of the Last-Modified header
    949    field from the selected (see <xref target="caching.negotiated.responses"/>)
    950    stored response, if available.
    951 </t>
    952 <t>
    953    Additionally, a cache &SHOULD; add an If-None-Match header field whose value is
    954    that of the ETag header field(s) from all responses stored for the requested URI,
    955    if present. However, if any of the stored responses contains only partial
    956    content, the cache &SHOULD-NOT; include its entity-tag in the If-None-Match
    957    header field unless the request is for a range that would be fully
    958    satisfied by that stored response.
     947   When sending such a conditional request, a cache adds an If-Modified-Since
     948   header field whose value is that of the Last-Modified header field from the
     949   selected (see <xref target="caching.negotiated.responses"/>) stored
     950   response, if available.
     951</t>
     952<t>
     953   Additionally, a cache can add an If-None-Match header field whose value is
     954   that of the ETag header field(s) from all responses stored for the
     955   requested URI, if present. However, if any of the stored responses contains
     956   only partial content, the cache shouldn't include its entity-tag in the
     957   If-None-Match header field unless the request is for a range that would be
     958   fully satisfied by that stored response.
    959959</t>
    960960
    … …  
    971971         A full response (i.e., one with a response body) indicates that none
    972972         of the stored responses nominated in the conditional request is
    973          suitable. Instead, a cache &SHOULD; use the full response to satisfy
    974          the request and &MAY; replace the stored response(s).
     973         suitable. Instead, the cache can use the full response to
     974         satisfy the request and &MAY; replace the stored response(s).
    975975      </t>
    976976      <t>
    977977         However, if a cache receives a 5xx response while attempting to
    978          validate a response, it &MAY; either forward this response to the
     978         validate a response, it can either forward this response to the
    979979         requesting client, or act as if the server failed to respond. In the
    980          latter case, it &MAY; return a previously stored response (see <xref
     980         latter case, it can return a previously stored response (see <xref
    981981         target="serving.stale.responses" />).
    982982      </t>
    … …  
    10481048</t>
    10491049<t>
    1050    A cache &SHOULD; invalidate the effective request URI
     1050   A cache &MUST; invalidate the effective request URI
    10511051   (&effective-request-uri;) when it receives a non-error response
    10521052   to a request with a method whose safety is unknown.
    … …  
    11411141</t>
    11421142<t>
    1143    If no selected response is available, the cache &MAY; forward the presented
     1143   If no selected response is available, the cache can forward the presented
    11441144   request to the origin server in a conditional request; see <xref
    11451145   target="validation.model"/>.
    … …  
    14661466      if a cache cannot reach the origin server for any reason, it &MUST;
    14671467      generate a 504 (Gateway Timeout) response.</t>
    1468       <t>A server &SHOULD; send the must-revalidate directive if and only if
    1469       failure to validate a request on the representation could result in
     1468      <t>The must-revalidate directive ought to be used by servers if and only
     1469      if failure to validate a request on the representation could result in
    14701470      incorrect operation, such as a silently unexecuted financial
    14711471      transaction.</t>
    … …  
    16641664</t>
    16651665<t>
    1666    When sending a no-cache request, a client &SHOULD; include both pragma and
    1667    cache-control directives unless Cache-Control: no-cache is purposefully
    1668    omitted to target other Cache-Control response directives at HTTP/1.1
    1669    caches. For example:
     1666   When sending a no-cache request, a client ought to include both the pragma
     1667   and cache-control directives, unless Cache-Control: no-cache is
     1668   purposefully omitted to target other Cache-Control response directives at
     1669   HTTP/1.1 caches. For example:
    16701670</t>
    16711671<figure>
    … …  
    17911791</t>
    17921792<t>
    1793    Systems that generate multiple Warning header fields &SHOULD; order them with
    1794    this user agent behavior in mind. New Warning header fields &SHOULD; be added
    1795    after any existing Warning headers fields.
     1793   Systems that generate multiple Warning header fields are encouraged to
     1794   order them with this user agent behavior in mind. New Warning header fields
     1795   are added after any existing Warning headers fields.
    17961796</t>
    17971797<t>
    … …  
    18451845   112 Disconnected operation
    18461846   <list>
    1847       <t>A cache &SHOULD; b include this if it is intentionally disconnected from
     1847      <t>A cache &SHOULD; include this if it is intentionally disconnected from
    18481848      the rest of the network for a period of time.</t>
    18491849   </list>
Note: See TracChangeset for help on using the changeset viewer.