Changeset 1922
- Timestamp:
- 01/10/12 05:18:23 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1921 r1922 919 919 <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a> <a id="header.content-type" href="#header.content-type">Content-Type</a></h3> 920 920 <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 921 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 922 type is that which would have been sent had the request been a GET. 921 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. 923 922 </p> 924 923 <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
r1921 r1922 320 320 representation, which defines both the data format and how that data 321 321 &SHOULD; be processed by the recipient (within the scope of the request 322 method semantics). For responses to the HEAD method, the media type is 322 method semantics) after any <x:ref>Content-Encoding</x:ref> is decoded. 323 For responses to the HEAD method, the media type is 323 324 that which would have been sent had the request been a GET. 324 325 </t>
Note: See TracChangeset
for help on using the changeset viewer.