Ignore:
Timestamp:
10/01/13 09:11:48 (10 years ago)
Author:
fielding@…
Message:

(editorial) add intro for proactive negotiation fields and clarify that they might apply to any response content, not just representations of the target resource

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2103 r2104  
    19721972
    19731973<section title="Content Negotiation" anchor="request.conneg">
     1974<t>
     1975   The following request header fields are sent by a user agent to engage in
     1976   <x:ref>proactive negotiation</x:ref> of the response content, as defined in
     1977   <xref target="proactive.negotiation"/>. The preferences sent in these
     1978   fields apply to any content in the response, including representations of
     1979   the target resource, representations of error or processing status, and
     1980   potentially even the miscellaneous text strings that might appear within
     1981   the protocol.
     1982</t>
    19741983<texttable align="left">
    19751984  <ttcol>Header Field Name</ttcol>
     
    19861995  <x:anchor-alias value="qvalue"/>
    19871996<t>
    1988    Many of the request header fields for proactive content negotiation
     1997   Many of the request header fields for <x:ref>proactive negotiation</x:ref>
    19891998   use a common parameter, named "q" (case-insensitive), to assign a relative
    19901999   "weight" to the preference for that associated kind of content.
     
    21432152<t>
    21442153   The "Accept-Charset" header field can be sent by a user agent to
    2145    indicate what charsets are acceptable in a selected representation.
     2154   indicate what charsets are acceptable in textual response content.
    21462155   This field allows user agents capable of understanding more comprehensive
    21472156   or special-purpose charsets to signal that capability to an origin server
    2148    that is capable of representing documents in those charsets.
     2157   that is capable of representing information in those charsets.
    21492158</t>
    21502159<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/>
Note: See TracChangeset for help on using the changeset viewer.