Ignore:
Timestamp:
Sep 2, 2012, 11:21:26 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) move payload section to immediately follow representation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1854 r1855  
    655655</section>
    656656
     657<section title="Payload" anchor="payload">
     658<t>
     659   HTTP messages &MAY; transfer a payload if not otherwise restricted by
     660   the request method or response status code.  The payload consists of
     661   metadata, in the form of header fields, and data, in the form of the
     662   sequence of octets in the message body after any transfer-coding has
     663   been decoded.
     664</t>
     665<iref item="payload"/>
     666<t>   
     667   A "<x:dfn>payload</x:dfn>" in HTTP is always a partial or complete
     668   representation of some resource.  We use separate terms for payload
     669   and representation because some messages contain only the associated
     670   representation's header fields (e.g., responses to HEAD) or only some
     671   part(s) of the representation (e.g., the <x:ref>206 (Partial Content)</x:ref>
     672   status code).
     673</t>
     674<section title="Payload Header Fields" anchor="payload.header.fields">
     675  <x:anchor-alias value="payload-header"/>
     676<t>
     677   HTTP header fields that specifically define the payload, rather than the
     678   associated representation, are referred to as "payload header fields".
     679   The following payload header fields are defined by HTTP/1.1:
     680</t>
     681<texttable align="left">
     682  <ttcol>Header Field Name</ttcol>
     683  <ttcol>Defined in...</ttcol>
     684
     685  <c>Content-Length</c> <c>&header-content-length;</c>
     686  <c>Content-Range</c> <c>&header-content-range;</c>
     687</texttable>
     688</section>
     689
     690<section title="Payload Body" anchor="payload.body">
     691  <x:anchor-alias value="payload-body"/>
     692<t>
     693   A payload body is only present in a message when a message body is
     694   present, as described in &message-body;. The payload body is obtained
     695   from the message body by decoding any <x:ref>Transfer-Encoding</x:ref> that
     696   might have been applied to ensure safe and proper transfer of the message.
     697</t>
     698</section>
     699</section>
     700
    657701<section title="Request Methods" anchor="methods">
    658702
     
    28362880<t>
    28372881   See <xref target="RFC5646"/> for further information.
    2838 </t>
    2839 </section>
    2840 </section>
    2841 
    2842 <section title="Payload" anchor="payload">
    2843 <t>
    2844    HTTP messages &MAY; transfer a payload if not otherwise restricted by
    2845    the request method or response status code.  The payload consists of
    2846    metadata, in the form of header fields, and data, in the form of the
    2847    sequence of octets in the message body after any transfer-coding has
    2848    been decoded.
    2849 </t>
    2850 <iref item="payload"/>
    2851 <t>   
    2852    A "<x:dfn>payload</x:dfn>" in HTTP is always a partial or complete
    2853    representation of some resource.  We use separate terms for payload
    2854    and representation because some messages contain only the associated
    2855    representation's header fields (e.g., responses to HEAD) or only some
    2856    part(s) of the representation (e.g., the <x:ref>206 (Partial Content)</x:ref>
    2857    status code).
    2858 </t>
    2859 <section title="Payload Header Fields" anchor="payload.header.fields">
    2860   <x:anchor-alias value="payload-header"/>
    2861 <t>
    2862    HTTP header fields that specifically define the payload, rather than the
    2863    associated representation, are referred to as "payload header fields".
    2864    The following payload header fields are defined by HTTP/1.1:
    2865 </t>
    2866 <texttable align="left">
    2867   <ttcol>Header Field Name</ttcol>
    2868   <ttcol>Defined in...</ttcol>
    2869 
    2870   <c>Content-Length</c> <c>&header-content-length;</c>
    2871   <c>Content-Range</c> <c>&header-content-range;</c>
    2872 </texttable>
    2873 </section>
    2874 
    2875 <section title="Payload Body" anchor="payload.body">
    2876   <x:anchor-alias value="payload-body"/>
    2877 <t>
    2878    A payload body is only present in a message when a message body is
    2879    present, as described in &message-body;. The payload body is obtained
    2880    from the message body by decoding any <x:ref>Transfer-Encoding</x:ref> that
    2881    might have been applied to ensure safe and proper transfer of the message.
    28822882</t>
    28832883</section>
Note: See TracChangeset for help on using the changeset viewer.