Ignore:
Timestamp:
May 20, 2008, 2:37:22 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #115: add qvalue defaulting for Accept-Encoding (closes #115).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r247 r248  
    445445         <tr>
    446446            <td class="header left"></td>
    447             <td class="header right">May 19, 2008</td>
     447            <td class="header right">May 20, 2008</td>
    448448         </tr>
    449449      </table>
     
    10041004                     #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] )
    10051005  <a href="#header.accept-encoding" class="smpl">codings</a>          = ( <a href="#content.codings" class="smpl">content-coding</a> | "*" )
    1006 </pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p>
     1006</pre><p id="rfc.section.6.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
     1007      </p>
     1008      <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
    10071009      <div id="rfc.figure.u.27"></div><pre class="text">    Accept-Encoding: compress, gzip
    10081010    Accept-Encoding:
     
    10101012    Accept-Encoding: compress;q=0.5, gzip;q=1.0
    10111013    Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
    1012 </pre><p id="rfc.section.6.3.p.5">A server tests whether a content-coding is acceptable, according to an Accept-Encoding field, using these rules: </p>
     1014</pre><p id="rfc.section.6.3.p.6">A server tests whether a content-coding is acceptable, according to an Accept-Encoding field, using these rules: </p>
    10131015      <ol>
    10141016         <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it
     
    10241026         </li>
    10251027      </ol>
    1026       <p id="rfc.section.6.3.p.6">If an Accept-Encoding field is present in a request, and if the server cannot send a response which is acceptable according
     1028      <p id="rfc.section.6.3.p.7">If an Accept-Encoding field is present in a request, and if the server cannot send a response which is acceptable according
    10271029         to the Accept-Encoding header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
    10281030      </p>
    1029       <p id="rfc.section.6.3.p.7">If no Accept-Encoding field is present in a request, the server <em class="bcp14">MAY</em> assume that the client will accept any content coding. In this case, if "identity" is one of the available content-codings,
     1031      <p id="rfc.section.6.3.p.8">If no Accept-Encoding field is present in a request, the server <em class="bcp14">MAY</em> assume that the client will accept any content coding. In this case, if "identity" is one of the available content-codings,
    10301032         then the server <em class="bcp14">SHOULD</em> use the "identity" content-coding, unless it has additional information that a different content-coding is meaningful to the
    10311033         client.
     
    15511553      <ul>
    15521554         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
     1555         </li>
     1556         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115</a>&gt;: "missing default for qvalue in description of Accept-Encoding"
    15531557         </li>
    15541558      </ul>
Note: See TracChangeset for help on using the changeset viewer.