Changeset 1163 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

Mar 10, 2011, 10:45:30 PM (9 years ago)

Author:

fielding@…

Message:

Remove header field classifications.

Addresses #224 and #104

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (14 diffs)

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

@@ -522 +522 @@
       <t>the request method associated with the stored response allows it to
       be used for the presented request, and</t>
-      <t>selecting request-header fields nominated by the stored response (if any)
+      <t>selecting header fields nominated by the stored response (if any)
       match those presented (see <xref target="caching.negotiated.responses"
       />), and</t>
@@ -690 +690 @@
 <section anchor="age.calculations" title="Calculating Age">
 <t>
-   HTTP/1.1 uses the Age response-header field to convey the estimated age of the
+   HTTP/1.1 uses the Age header field to convey the estimated age of the
    response message when obtained from a cache. The Age field value is the
    cache's estimate of the amount of time since the response was generated or
@@ -940 +940 @@
    When a cache receives a request that can be satisfied by a stored response
    that has a Vary header field (<xref target="header.vary"/>), it &MUST-NOT;
-   use that response unless all of the selecting request-header fields nominated by
+   use that response unless all of the selecting header fields nominated by
    the Vary header field match in both the original request (i.e., that associated
    with the stored response), and the presented request.
 </t>
 <t>
-   The selecting request-header fields from two requests are defined to match if and
+   The selecting header fields from two requests are defined to match if and
    only if those in the first request can be transformed to those in the
    second request by applying any of the following:
@@ -953 +953 @@
       </t>
       <t>
-         combining multiple message-header fields with the same field name
+         combining multiple header fields with the same field name
          (see &header-fields;)
       </t>
@@ -975 +975 @@
 </t>
 <t>
-   The stored response with matching selecting request-header fields is known as the
+   The stored response with matching selecting header fields is known as the
    selected response.
 </t>
@@ -1040 +1040 @@
    <x:anchor-alias value="age-value"/>
 <t>
-   The "Age" response-header field conveys the sender's estimate of the amount
+   The "Age" header field conveys the sender's estimate of the amount
    of time since the response was generated or successfully validated at the
    origin server. Age values are calculated as specified in <xref
@@ -1081 +1081 @@
    <x:anchor-alias value="cache-response-directive"/>
 <t>
-   The "Cache-Control" general-header field is used to specify directives for
+   The "Cache-Control" header field is used to specify directives for
    caches along the request/response chain. Such cache directives are
    unidirectional in that the presence of a directive in a request does not
@@ -1506 +1506 @@
    <x:anchor-alias value="pragma-directive"/>
 <t>
-   The "Pragma" general-header field is used to include
+   The "Pragma" header field is used to include
    implementation-specific directives that might apply to any recipient along
    the request/response chain. All pragma directives specify optional behavior
@@ -1532 +1532 @@
    <t>
       <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" as a
-      response-header field is not actually specified, it does not provide a
+      header field is not actually specified, it does not provide a
       reliable replacement for "Cache-Control: no-cache" in a response.
    </t>
@@ -1548 +1548 @@
    <x:anchor-alias value="Vary-v"/>
 <t>
-   The "Vary" response-header field conveys the set of request-header fields
+   The "Vary" header field conveys the set of header fields
    that were used to select the representation.
 </t>
@@ -1569 +1569 @@
 <t>
    The set of header fields named by the Vary field value is known as the
-   selecting request-header fields.
+   selecting header fields.
 </t>
 <t>
@@ -1583 +1583 @@
 <t>
    A Vary field value of "*" signals that unspecified parameters not limited
-   to the request-header fields (e.g., the network address of the client), play a
+   to the header fields (e.g., the network address of the client), play a
    role in the selection of the response representation; therefore, a cache
    cannot determine whether this response is appropriate. A proxy &MUST-NOT;
@@ -1589 +1589 @@
 </t>
 <t>
-   The field-names given are not limited to the set of standard request-header
+   The field-names given are not limited to the set of standard header
    fields defined by this specification. Field names are case-insensitive.
 </t>
@@ -1605 +1605 @@
    <x:anchor-alias value="warn-text"/>
 <t>
-   The "Warning" general-header field is used to carry additional information
+   The "Warning" header field is used to carry additional information
    about the status or transformation of a message that might not be reflected
    in the message. This information is typically used to warn about possible