Changeset 248
- Timestamp:
- 20/05/08 09:37:22 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r247 r248 445 445 <tr> 446 446 <td class="header left"></td> 447 <td class="header right">May 19, 2008</td>447 <td class="header right">May 20, 2008</td> 448 448 </tr> 449 449 </table> … … 1004 1004 #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 1005 1005 <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> 1007 1009 <div id="rfc.figure.u.27"></div><pre class="text"> Accept-Encoding: compress, gzip 1008 1010 Accept-Encoding: … … 1010 1012 Accept-Encoding: compress;q=0.5, gzip;q=1.0 1011 1013 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> 1013 1015 <ol> 1014 1016 <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it … … 1024 1026 </li> 1025 1027 </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 according1028 <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 1027 1029 to the Accept-Encoding header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code. 1028 1030 </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, 1030 1032 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 1031 1033 client. … … 1551 1553 <ul> 1552 1554 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105</a>>: "Classification for Allow header" 1555 </li> 1556 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115</a>>: "missing default for qvalue in description of Accept-Encoding" 1553 1557 </li> 1554 1558 </ul> -
draft-ietf-httpbis/latest/p3-payload.xml
r244 r248 1089 1089 <x:ref>codings</x:ref> = ( <x:ref>content-coding</x:ref> | "*" ) 1090 1090 </artwork></figure> 1091 <t> 1092 Each codings value &MAY; be given an associated quality value which 1093 represents the preference for that encoding. The default value is q=1. 1094 </t> 1091 1095 <t> 1092 1096 Examples of its use are: … … 2504 2508 "Classification for Allow header" 2505 2509 </t> 2510 <t> 2511 <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/115"/>: 2512 "missing default for qvalue in description of Accept-Encoding" 2513 </t> 2506 2514 </list> 2507 2515 </t>
Note: See TracChangeset
for help on using the changeset viewer.