Changeset 1905 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 18/09/12 09:26:12 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1901 r1905 304 304 of data (representation body). 305 305 </t> 306 <t> 307 HTTP messages can transfer a full or partial representation in the payload 308 (<xref target="payload"/>) if not otherwise restricted by the request 309 method or response status code. In a request, the purpose of such a 310 representation is defined by the method semantics. In a response, the 311 purpose is defined by both the request method and the response status code. 306 307 <section title="Message Payload" anchor="payload"> 308 <iref item="payload"/> 309 <t> 310 Some HTTP messages transfer a complete or partial representation as the 311 message "<x:dfn>payload</x:dfn>". In some cases, a payload might only 312 contain the associated representation's header fields (e.g., responses to 313 HEAD) or only some part(s) of the representation body 314 (e.g., the <x:ref>206 (Partial Content)</x:ref> status code). 315 </t> 316 <t> 317 The purpose of a payload in a request is defined by the method semantics. 318 In a response, the payload's purpose is defined by both the request method 319 and the response status code. 312 320 </t> 313 321 <t> … … 331 339 for resolving it. 332 340 </t> 341 <t> 342 Header fields that specifically describe the payload, rather than the 343 associated representation, are referred to as "payload header fields". 344 Payload header fields are defined in other parts of this specification, 345 due to their impact on message parsing. 346 </t> 347 <texttable align="left"> 348 <ttcol>Header Field Name</ttcol> 349 <ttcol>Defined in...</ttcol> 350 351 <c>Content-Length</c> <c>&header-content-length;</c> 352 <c>Content-Range</c> <c>&header-content-range;</c> 353 <c>Transfer-Encoding</c> <c>&header-transfer-encoding;</c> 354 </texttable> 355 </section> 333 356 334 357 <section title="Associating a Representation with its Resource" anchor="associating.representation.with.resource"> … … 845 868 </t> 846 869 </section> 847 </section>848 </section>849 850 <section title="Payload" anchor="payload">851 <t>852 HTTP messages &MAY; transfer a payload if not otherwise restricted by853 the request method or response status code. The payload consists of854 metadata, in the form of header fields, and data, in the form of the855 sequence of octets in the message body after any transfer-coding has856 been decoded.857 </t>858 <iref item="payload"/>859 <t>860 A "<x:dfn>payload</x:dfn>" in HTTP is always a partial or complete861 representation of some resource. We use separate terms for payload862 and representation because some messages contain only the associated863 representation's header fields (e.g., responses to HEAD) or only some864 part(s) of the representation (e.g., the <x:ref>206 (Partial Content)</x:ref>865 status code).866 </t>867 <section title="Payload Header Fields" anchor="payload.header.fields">868 <x:anchor-alias value="payload-header"/>869 <t>870 HTTP header fields that specifically define the payload, rather than the871 associated representation, are referred to as "payload header fields".872 The following payload header fields are defined by HTTP/1.1:873 </t>874 <texttable align="left">875 <ttcol>Header Field Name</ttcol>876 <ttcol>Defined in...</ttcol>877 878 <c>Content-Length</c> <c>&header-content-length;</c>879 <c>Content-Range</c> <c>&header-content-range;</c>880 </texttable>881 </section>882 883 <section title="Payload Body" anchor="payload.body">884 <x:anchor-alias value="payload-body"/>885 <t>886 A payload body is only present in a message when a message body is887 present, as described in &message-body;. The payload body is obtained888 from the message body by decoding any <x:ref>Transfer-Encoding</x:ref> that889 might have been applied to ensure safe and proper transfer of the message.890 </t>891 870 </section> 892 871 </section>
Note: See TracChangeset
for help on using the changeset viewer.