Ignore:
Timestamp:
05/01/13 08:21:45 (10 years ago)
Author:
fielding@…
Message:

(editorial) Clarify that no Accept-Encoding means that the user agent has no prefereence, not that it must implement all possible codings; addresses #424

File:
1 edited

Legend:

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

    r2083 r2084  
    21952195   Each codings value &MAY; be given an associated quality value
    21962196   representing the preference for that encoding, as defined in &qvalue;.
     2197   The asterisk "*" symbol in an Accept-Encoding field matches any available
     2198   content-coding not explicitly listed in the header field.
    21972199</t>
    21982200<t>
     
    22072209</artwork></figure>
    22082210<t>
     2211   A request without an Accept-Encoding header field implies that the user
     2212   agent has no preferences regarding content-codings. Although this allows
     2213   the server to use any content-coding in a response, it does not imply that
     2214   the user agent will be able to correctly process all encodings.
     2215</t>
     2216<t>
    22092217   A server tests whether a content-coding for a given representation is
    2210    acceptable, according to an Accept-Encoding field, using these rules:
     2218   acceptable using these rules:
    22112219  <list style="numbers">
    2212       <t>The special "*" symbol in an Accept-Encoding field matches any
    2213          available content-coding not explicitly listed in the header
    2214          field.</t>
     2220      <t>If no Accept-Encoding field is in the request, any content-coding is
     2221         considered acceptable by the user agent.</t>
    22152222
    22162223      <t>If the representation has no content-coding, then it is acceptable
     
    22362243   without any content-coding.
    22372244</t>
    2238 <t>
    2239    A request without an Accept-Encoding header field implies that the user
    2240    agent will accept any content-coding in response.
    2241 </t>
    22422245<x:note>
    22432246  <t>
    22442247    &Note; Most HTTP/1.0 applications do not recognize or obey qvalues
    2245     associated with content-codings. This means that qvalues will not
     2248    associated with content-codings. This means that qvalues might not
    22462249    work and are not permitted with x-gzip or x-compress.
    22472250  </t>
Note: See TracChangeset for help on using the changeset viewer.