Ignore:
Timestamp:
Mar 10, 2011, 10:45:30 PM (9 years ago)
Author:
fielding@…
Message:

Remove header field classifications.

Addresses #224 and #104

File:
1 edited

Legend:

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

    r1145 r1163  
    522522      <t>the request method associated with the stored response allows it to
    523523      be used for the presented request, and</t>
    524       <t>selecting request-header fields nominated by the stored response (if any)
     524      <t>selecting header fields nominated by the stored response (if any)
    525525      match those presented (see <xref target="caching.negotiated.responses"
    526526      />), and</t>
     
    690690<section anchor="age.calculations" title="Calculating Age">
    691691<t>
    692    HTTP/1.1 uses the Age response-header field to convey the estimated age of the
     692   HTTP/1.1 uses the Age header field to convey the estimated age of the
    693693   response message when obtained from a cache. The Age field value is the
    694694   cache's estimate of the amount of time since the response was generated or
     
    940940   When a cache receives a request that can be satisfied by a stored response
    941941   that has a Vary header field (<xref target="header.vary"/>), it &MUST-NOT;
    942    use that response unless all of the selecting request-header fields nominated by
     942   use that response unless all of the selecting header fields nominated by
    943943   the Vary header field match in both the original request (i.e., that associated
    944944   with the stored response), and the presented request.
    945945</t>
    946946<t>
    947    The selecting request-header fields from two requests are defined to match if and
     947   The selecting header fields from two requests are defined to match if and
    948948   only if those in the first request can be transformed to those in the
    949949   second request by applying any of the following:
     
    953953      </t>
    954954      <t>
    955          combining multiple message-header fields with the same field name
     955         combining multiple header fields with the same field name
    956956         (see &header-fields;)
    957957      </t>
     
    975975</t>
    976976<t>
    977    The stored response with matching selecting request-header fields is known as the
     977   The stored response with matching selecting header fields is known as the
    978978   selected response.
    979979</t>
     
    10401040   <x:anchor-alias value="age-value"/>
    10411041<t>
    1042    The "Age" response-header field conveys the sender's estimate of the amount
     1042   The "Age" header field conveys the sender's estimate of the amount
    10431043   of time since the response was generated or successfully validated at the
    10441044   origin server. Age values are calculated as specified in <xref
     
    10811081   <x:anchor-alias value="cache-response-directive"/>
    10821082<t>
    1083    The "Cache-Control" general-header field is used to specify directives for
     1083   The "Cache-Control" header field is used to specify directives for
    10841084   caches along the request/response chain. Such cache directives are
    10851085   unidirectional in that the presence of a directive in a request does not
     
    15061506   <x:anchor-alias value="pragma-directive"/>
    15071507<t>
    1508    The "Pragma" general-header field is used to include
     1508   The "Pragma" header field is used to include
    15091509   implementation-specific directives that might apply to any recipient along
    15101510   the request/response chain. All pragma directives specify optional behavior
     
    15321532   <t>
    15331533      <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" as a
    1534       response-header field is not actually specified, it does not provide a
     1534      header field is not actually specified, it does not provide a
    15351535      reliable replacement for "Cache-Control: no-cache" in a response.
    15361536   </t>
     
    15481548   <x:anchor-alias value="Vary-v"/>
    15491549<t>
    1550    The "Vary" response-header field conveys the set of request-header fields
     1550   The "Vary" header field conveys the set of header fields
    15511551   that were used to select the representation.
    15521552</t>
     
    15691569<t>
    15701570   The set of header fields named by the Vary field value is known as the
    1571    selecting request-header fields.
     1571   selecting header fields.
    15721572</t>
    15731573<t>
     
    15831583<t>
    15841584   A Vary field value of "*" signals that unspecified parameters not limited
    1585    to the request-header fields (e.g., the network address of the client), play a
     1585   to the header fields (e.g., the network address of the client), play a
    15861586   role in the selection of the response representation; therefore, a cache
    15871587   cannot determine whether this response is appropriate. A proxy &MUST-NOT;
     
    15891589</t>
    15901590<t>
    1591    The field-names given are not limited to the set of standard request-header
     1591   The field-names given are not limited to the set of standard header
    15921592   fields defined by this specification. Field names are case-insensitive.
    15931593</t>
     
    16051605   <x:anchor-alias value="warn-text"/>
    16061606<t>
    1607    The "Warning" general-header field is used to carry additional information
     1607   The "Warning" header field is used to carry additional information
    16081608   about the status or transformation of a message that might not be reflected
    16091609   in the message. This information is typically used to warn about possible
Note: See TracChangeset for help on using the changeset viewer.