Changeset 2250


Ignore:
Timestamp:
May 16, 2013, 6:45:39 PM (6 years ago)
Author:
mnot@…
Message:

Fix misused SHOULDs in p6 for #472

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

Legend:

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

    r2249 r2250  
    452452  }
    453453  @bottom-center {
    454        content: "Expires November 9, 2013";
     454       content: "Expires November 18, 2013";
    455455  }
    456456  @bottom-right {
     
    492492      <link href="p5-range.html" rel="prev">
    493493      <link href="p7-auth.html" rel="next">
    494       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     494      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    495495      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    496496      <meta name="dct.creator" content="Fielding, R.">
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2013-05-08">
     500      <meta name="dct.issued" scheme="ISO8601" content="2013-05-17">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: November 9, 2013</td>
     526               <td class="left">Expires: November 18, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">May 8, 2013</td>
     535               <td class="right">May 17, 2013</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on November 9, 2013.</p>
     561      <p>This Internet-Draft will expire on November 18, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    985985  corrected_age_value = age_value + response_delay; 
    986986</pre><div id="rfc.figure.u.4"></div>
    987       <p>These <em class="bcp14">SHOULD</em> be combined as
    988       </p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
     987      <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
    989988</pre><p id="rfc.section.4.1.3.p.11">unless the cache is confident in the value of the <a href="#header.age" class="smpl">Age</a> header field (e.g., because there are no HTTP/1.0 hops in the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
    990989      </p>
     
    10081007      </p>
    10091008      <div id="rfc.iref.f.3"></div>
    1010       <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache shouldn't attempt to validate a response simply because
     1009      <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache ought not attempt to validate a response simply because
    10111010         that response became stale in transit.
    10121011      </p>
     
    10231022      </p>
    10241023      <p id="rfc.section.4.2.p.4">Another is the <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field, whose value is that of the <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field(s) from relevant responses stored for the primary cache key, if present. However, if any of the stored responses
    1025          contains only partial content, the cache shouldn't include its entity-tag in the If-None-Match header field unless the request
     1024         contains only partial content, the cache ought not include its entity-tag in the If-None-Match header field unless the request
    10261025         is for a range that would be fully satisfied by that stored response.
    10271026      </p>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2249 r2250  
    708708</figure>
    709709<figure>
    710 <preamble>These &SHOULD; be combined as</preamble>
     710<preamble>These are combined as</preamble>
    711711<artwork type="code">
    712712  corrected_initial_age = max(apparent_age, corrected_age_value);
     
    762762   response is no longer fresh, the cache &MAY; forward it to the requesting
    763763   client without adding a new <x:ref>Warning</x:ref> (but without removing
    764    any existing Warning header fields). A cache shouldn't attempt to validate
     764   any existing Warning header fields). A cache ought not attempt to validate
    765765   a response simply because that response became stale in transit.
    766766</t>
     
    796796   relevant responses stored for the primary cache key, if present. However,
    797797   if any of the stored responses contains only partial content, the cache
    798    shouldn't include its entity-tag in the If-None-Match header field unless
     798   ought not include its entity-tag in the If-None-Match header field unless
    799799   the request is for a range that would be fully satisfied by that stored
    800800   response.
Note: See TracChangeset for help on using the changeset viewer.