Ignore:
Timestamp:
12/06/13 08:26:28 (7 years ago)
Author:
julian.reschke@…
Message:

Add fallback discussion for Accept-Language (see #448). Also tune the statements for other Accept-* header fields (MAY->can).

File:
1 edited

Legend:

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

    r2288 r2291  
    21272127<t>
    21282128   A request without any Accept header field implies that the user agent
    2129    will accept any media type in response.
    2130    If an Accept header field is present in a request and none of the
    2131    available representations for the response have a media type that is
    2132    listed as acceptable, the origin server &MAY; either honor the Accept
    2133    header field by sending a <x:ref>406 (Not Acceptable)</x:ref> response
    2134    or disregard the Accept header field by treating the response as if
    2135    it is not subject to content negotiation.
     2129   will accept any media type in response. If the header field is present in a
     2130   request and none of the available representations for the response have a
     2131   media type that is listed as acceptable, the origin server can either honor
     2132   the header field by sending a <x:ref>406 (Not Acceptable)</x:ref> response
     2133   or disregard the header field by treating the response as if it is not
     2134   subject to content negotiation.
    21362135</t>
    21372136<t>
     
    22252224<t>
    22262225   A request without any Accept-Charset header field implies that the user
    2227    agent will accept any charset in response.
    2228    Most general-purpose user agents do not send Accept-Charset, unless
    2229    specifically configured to do so, because a detailed list of supported
    2230    charsets makes it easier for a server to identify an individual by virtue
    2231    of the user agent's request characteristics (<xref target="fingerprinting"/>).
     2226   agent will accept any charset in response. Most general-purpose user agents
     2227   do not send Accept-Charset, unless specifically configured to do so, because
     2228   a detailed list of supported charsets makes it easier for a server to
     2229   identify an individual by virtue of the user agent's request characteristics
     2230   (<xref target="fingerprinting"/>).
    22322231</t>
    22332232<t>
    22342233   If an Accept-Charset header field is present in a request and none of the
    22352234   available representations for the response has a charset that is listed as
    2236    acceptable, the origin server &MAY; either honor the Accept-Charset header
    2237    field, by sending a <x:ref>406 (Not Acceptable)</x:ref> response, or
    2238    disregard the Accept-Charset header field by treating the resource as if
    2239    it is not subject to content negotiation.
     2235   acceptable, the origin server can either honor the header field, by sending a
     2236   <x:ref>406 (Not Acceptable)</x:ref> response, or disregard the header field by
     2237   treating the resource as if it is not subject to content negotiation.
    22402238</t>
    22412239</section>
     
    23402338   would mean: "I prefer Danish, but will accept British English and
    23412339   other types of English".
     2340</t>
     2341<t>
     2342   A request without any Accept-Language header field implies that the user
     2343   agent will accept any language in response. If the header field is present
     2344   in a request and none of the available representations for the response have
     2345   a matching language tag, the origin server can either disregard the header
     2346   field by treating the response as if it is not subject to content
     2347   negotiation, or honor the header field by sending a <x:ref>406 (Not Acceptable)</x:ref>
     2348   response. However, the latter is not encouraged, as doing so can prevent
     2349   users from accessing content that they might be able to use (with
     2350   translation software, for example).
    23422351</t>
    23432352<t>
     
    63446353    </t>
    63456354    <t>
     6355      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448"/>:
     6356      "Fallback for Accept-Language"
     6357    </t>
     6358    <t>
    63466359      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/449"/>:
    63476360      "Receiving a higher minor HTTP version number"
Note: See TracChangeset for help on using the changeset viewer.