Changeset 1922

Timestamp:

01/10/12 05:18:23 (10 years ago)

Author:

fielding@…

Message:

(editorial) clarify that content-type applies after any content-encoding is decoded

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (1 diff)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -919 +919 @@
       <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h3>
       <p id="rfc.section.3.1.1.p.1">The "Content-Type" header field indicates the media type of the representation, which defines both the data format and how
-         that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). For responses to the HEAD method, the media
-         type is that which would have been sent had the request been a GET.
+         that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics) after any <a href="#header.content-encoding" class="smpl">Content-Encoding</a> is decoded. For responses to the HEAD method, the media type is that which would have been sent had the request been a GET.
       </p>
       <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -320 +320 @@
    representation, which defines both the data format and how that data
    &SHOULD; be processed by the recipient (within the scope of the request
-   method semantics). For responses to the HEAD method, the media type is
+   method semantics) after any <x:ref>Content-Encoding</x:ref> is decoded.
+   For responses to the HEAD method, the media type is
    that which would have been sent had the request been a GET.
 </t>