Changeset 2073

Timestamp:

31/12/12 11:02:54 (10 years ago)

Author:

fielding@…

Message:

fix several more cases of include being used instead of send or generate, and a few requirements that are simply facts

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (3 diffs)
• p2-semantics.xml (modified) (3 diffs)
• p5-range.html (modified) (6 diffs)
• p5-range.xml (modified) (1 diff)
• p6-cache.html (modified) (6 diffs)
• p6-cache.xml (modified) (4 diffs)

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

@@ -2098 +2098 @@
       <p id="rfc.section.5.5.3.p.1">The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers
          to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user
-         agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> include a User-Agent field in each request unless specifically configured not to do so.
+         agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> send a User-Agent field in each request unless specifically configured not to do so.
       </p>
       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
@@ -2726 +2726 @@
       <div id="rfc.iref.s.6"></div>
       <p id="rfc.section.6.6.p.1">The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method.
-         Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
+         Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
          User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
       </p>
@@ -2813 +2813 @@
 </pre><p id="rfc.section.7.1.1.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
       </p>
-      <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
-         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
-         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
+      <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps are represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is
+         exactly equal to UTC (Coordinated Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as
+         the three-letter abbreviation for time zone, and is assumed when reading the asctime format. HTTP-date is case sensitive.
+         A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar.
       </p>
       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.39"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>

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

@@ -2439 +2439 @@
    the scope of reported interoperability problems, to work around or tailor
    responses to avoid particular user agent limitations, and for analytics
-   regarding browser or operating system use. A user agent &SHOULD; include
+   regarding browser or operating system use. A user agent &SHOULD; send
    a User-Agent field in each request unless specifically configured not
    to do so.
@@ -3389 +3389 @@
 <t>
    The <x:dfn>5xx (Server Error)</x:dfn> class of status code indicates that
-   the server is aware that it has erred or is incapable of
-   performing the requested method. Except when responding to a HEAD request, the
-   server &SHOULD; include a representation containing an explanation of the
-   error situation, and whether it is a temporary or permanent
-   condition. User agents &SHOULD; display any included representation to the
-   user. These response codes are applicable to any request method.
+   the server is aware that it has erred or is incapable of performing the
+   requested method.
+   Except when responding to a HEAD request, the server &SHOULD; send a
+   representation containing an explanation of the error situation, and
+   whether it is a temporary or permanent condition.
+   User agents &SHOULD; display any included representation to the user.
+   These response codes are applicable to any request method.
 </t>
 
@@ -3532 +3533 @@
 </t>
 <t>
-   All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time
+   All HTTP date/time stamps are represented in Greenwich Mean Time
    (GMT), without exception. For the purposes of HTTP, GMT is exactly
    equal to UTC (Coordinated Universal Time). This is indicated in the
    first two formats by the inclusion of "GMT" as the three-letter
-   abbreviation for time zone, and &MUST; be assumed when reading the
-   asctime format. HTTP-date is case sensitive and &MUST-NOT; include
-   additional whitespace beyond that specifically included as SP in the
-   grammar.
+   abbreviation for time zone, and is assumed when reading the
+   asctime format. HTTP-date is case sensitive. A sender &MUST-NOT; generate
+   additional whitespace in an HTTP-date beyond that specifically included as
+   SP in the grammar.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/>

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires July 3, 2013"; 
+       content: "Expires July 4, 2013"; 
   } 
   @bottom-right {
@@ -493 +493 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-12-30">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-12-31">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -519 +519 @@
             </tr>
             <tr>
-               <td class="left">Expires: July 3, 2013</td>
+               <td class="left">Expires: July 4, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -528 +528 @@
             <tr>
                <td class="left"></td>
-               <td class="right">December 30, 2012</td>
+               <td class="right">December 31, 2012</td>
             </tr>
          </tbody>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on July 3, 2013.</p>
+      <p>This Internet-Draft will expire on July 4, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -803 +803 @@
       </p>
       <p id="rfc.section.5.2.p.7">In the case of a byte range request: a server sending a response with status code <a href="#status.416" class="smpl">416 (Requested Range Not
-            Satisfiable)</a>  <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
-         selected resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a>  <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
+            Satisfiable)</a>  <em class="bcp14">SHOULD</em> send a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the selected
+         resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a>  <em class="bcp14">MUST NOT</em> send a Content-Range field with a byte-range-resp-spec of "*".
       </p>
       <p id="rfc.section.5.2.p.8">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. Currently,

draft-ietf-httpbis/latest/p5-range.xml

@@ -522 +522 @@
    In the case of a byte range request:
    a server sending a response with status code <x:ref>416 (Requested Range Not
-   Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
+   Satisfiable)</x:ref> &SHOULD; send a Content-Range field with a byte-range-resp-spec
    of "*". The instance-length specifies the current length of
    the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref>
-   &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
+   &MUST-NOT; send a Content-Range field with a byte-range-resp-spec of "*".
 </t>
 <t>

draft-ietf-httpbis/latest/p6-cache.html

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires July 3, 2013"; 
+       content: "Expires July 4, 2013"; 
   } 
   @bottom-right {
@@ -498 +498 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-12-30">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-12-31">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: July 3, 2013</td>
+               <td class="left">Expires: July 4, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">December 30, 2012</td>
+               <td class="right">December 31, 2012</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on July 3, 2013.</p>
+      <p>This Internet-Draft will expire on July 4, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1524 +1524 @@
       <div id="rfc.iref.52"></div>
       <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="warn.110" href="#warn.110">110 Response is Stale</a></h3>
-      <p id="rfc.section.7.5.1.p.1">A cache <em class="bcp14">SHOULD</em> include this whenever the sent response is stale.
+      <p id="rfc.section.7.5.1.p.1">A cache <em class="bcp14">SHOULD</em> generate this whenever the sent response is stale.
       </p>
       <div id="rfc.iref.52"></div>
       <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="warn.111" href="#warn.111">111 Revalidation Failed</a></h3>
-      <p id="rfc.section.7.5.2.p.1">A cache <em class="bcp14">SHOULD</em> include this when sending a stale response because an attempt to validate the response failed, due to an inability to reach
+      <p id="rfc.section.7.5.2.p.1">A cache <em class="bcp14">SHOULD</em> generate this when sending a stale response because an attempt to validate the response failed, due to an inability to reach
          the server.
       </p>
       <div id="rfc.iref.52"></div>
       <h3 id="rfc.section.7.5.3"><a href="#rfc.section.7.5.3">7.5.3</a>&nbsp;<a id="warn.112" href="#warn.112">112 Disconnected Operation</a></h3>
-      <p id="rfc.section.7.5.3.p.1">A cache <em class="bcp14">SHOULD</em> include this if it is intentionally disconnected from the rest of the network for a period of time.
+      <p id="rfc.section.7.5.3.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it is intentionally disconnected from the rest of the network for a period of time.
       </p>
       <div id="rfc.iref.52"></div>
       <h3 id="rfc.section.7.5.4"><a href="#rfc.section.7.5.4">7.5.4</a>&nbsp;<a id="warn.113" href="#warn.113">113 Heuristic Expiration</a></h3>
-      <p id="rfc.section.7.5.4.p.1">A cache <em class="bcp14">SHOULD</em> include this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than 24
-         hours.
+      <p id="rfc.section.7.5.4.p.1">A cache <em class="bcp14">SHOULD</em> generate this if it heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater than
+         24 hours.
       </p>
       <div id="rfc.iref.52"></div>

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

@@ -1783 +1783 @@
   <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this whenever the sent response is stale.
+   A cache &SHOULD; generate this whenever the sent response is stale.
 </t>
 </section>
@@ -1790 +1790 @@
   <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this when sending a stale response because an
+   A cache &SHOULD; generate this when sending a stale response because an
    attempt to validate the response failed, due to an inability to reach
    the server.
@@ -1799 +1799 @@
   <iref primary="true" item="112 Disconnected Operation (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this if it is intentionally disconnected from
+   A cache &SHOULD; generate this if it is intentionally disconnected from
    the rest of the network for a period of time.
 </t>
@@ -1807 +1807 @@
   <iref primary="true" item="113 Heuristic Expiration (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this if it heuristically chose a freshness
+   A cache &SHOULD; generate this if it heuristically chose a freshness
    lifetime greater than 24 hours and the response's age is greater than 24
    hours.