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/p3-payload.xml

    r1161 r1163  
    908908</t>
    909909<t>
    910    HTTP/1.1 includes the following request-header fields for enabling
     910   HTTP/1.1 includes the following header fields for enabling
    911911   server-driven negotiation through description of user agent
    912912   capabilities and user preferences: Accept (<xref target="header.accept"/>), Accept-Charset
     
    914914   (<xref target="header.accept-language"/>), and User-Agent (&header-user-agent;).
    915915   However, an origin server is not limited to these dimensions and &MAY; vary
    916    the response based on any aspect of the request, including information
    917    outside the request-header fields or within extension header fields
    918    not defined by this specification.
     916   the response based on any aspect of the request, including aspects
     917   of the connection (e.g., IP address) or information within extension
     918   header fields not defined by this specification.
    919919</t>
    920920<x:note>
     
    983983  <x:anchor-alias value="media-range"/>
    984984<t>
    985    The "Accept" request-header field can be used by user agents to specify
     985   The "Accept" header field can be used by user agents to specify
    986986   response media types that are acceptable. Accept header fields can be used to
    987987   indicate that the request is specifically limited to a small set of desired
     
    11081108  <x:anchor-alias value="Accept-Charset-v"/>
    11091109<t>
    1110    The "Accept-Charset" request-header field can be used by user agents to
     1110   The "Accept-Charset" header field can be used by user agents to
    11111111   indicate what response character sets are acceptable. This field allows
    11121112   clients capable of understanding more comprehensive or special-purpose
     
    11531153  <x:anchor-alias value="codings"/>
    11541154<t>
    1155    The "Accept-Encoding" request-header field can be used by user agents to
     1155   The "Accept-Encoding" header field can be used by user agents to
    11561156   indicate what response content-codings (<xref target="content.codings"/>)
    11571157   are acceptable in the response.
     
    12431243  <x:anchor-alias value="language-range"/>
    12441244<t>
    1245    The "Accept-Language" request-header field can be used by user agents to
     1245   The "Accept-Language" header field can be used by user agents to
    12461246   indicate the set of natural languages that are preferred in the response.
    12471247   Language tags are defined in <xref target="language.tags"/>.
     
    17361736<section title="Privacy Issues Connected to Accept Header Fields" anchor="privacy.issues.connected.to.accept.header.fields">
    17371737<t>
    1738    Accept request-headers fields can reveal information about the user to all
     1738   Accept headers fields can reveal information about the user to all
    17391739   servers which are accessed. The Accept-Language header field in particular
    17401740   can reveal information the user would consider to be of a private
     
    17501750   to omit the sending of Accept-Language header fields by default, and to ask
    17511751   the user whether or not to start sending Accept-Language header fields to a
    1752    server if it detects, by looking for any Vary response-header fields
     1752   server if it detects, by looking for any Vary header fields
    17531753   generated by the server, that such sending could improve the quality
    17541754   of service.
     
    25262526<t>
    25272527   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
    2528    include a single MIME-Version general-header field to indicate what
     2528   include a single MIME-Version header field to indicate what
    25292529   version of the MIME protocol was used to construct the message. Use
    25302530   of the MIME-Version header field indicates that the message is in
Note: See TracChangeset for help on using the changeset viewer.