Changeset 248 for draft-ietf-httpbis/latest/p3-payload.html

Timestamp:

20/05/08 09:37:22 (14 years ago)

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p3-payload.html (modified) (5 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -445 +445 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">May 19, 2008</td>
+            <td class="header right">May 20, 2008</td>
          </tr>
       </table>
@@ -1004 +1004 @@
                      #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] )
   <a href="#header.accept-encoding" class="smpl">codings</a>          = ( <a href="#content.codings" class="smpl">content-coding</a> | "*" )
-</pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p>
+</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.
+      </p>
+      <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
       <div id="rfc.figure.u.27"></div><pre class="text">    Accept-Encoding: compress, gzip
     Accept-Encoding:
@@ -1010 +1012 @@
     Accept-Encoding: compress;q=0.5, gzip;q=1.0
     Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
-</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>
+</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>
       <ol>
          <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>
       </ol>
-      <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
+      <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
          to the Accept-Encoding header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code.
       </p>
-      <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,
+      <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,
          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
          client. 
@@ -1551 +1553 @@
       <ul>
          <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"
+         </li>
+         <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"
          </li>
       </ul>