Changeset 864 for draft-ietf-httpbis
- Timestamp:
- 22/07/10 06:43:10 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r859 r864 1054 1054 differ only in the start-line, which is either a Request-Line (for requests) 1055 1055 or a Status-Line (for responses), and in the algorithm for determining 1056 the length of the message-body (<xref target="message.body .length"/>).1056 the length of the message-body (<xref target="message.body"/>). 1057 1057 In theory, a client could receive requests and a server could receive 1058 1058 responses, distinguishing them by their different start-line formats, … … 1270 1270 &MAY; be of zero length. 1271 1271 </t> 1272 <t anchor="message.body.length">1272 <t> 1273 1273 The length of the message-body is determined by one of the following 1274 1274 (in order of precedence): … … 1971 1971 is used, it &MUST; be the last transfer-coding applied to form the 1972 1972 message-body. The "chunked" transfer-coding &MUST-NOT; be applied more 1973 than once to a message-body. These rules allow the recipient to 1974 determine the message-body length of the message (<xref target="message.body.length"/>). 1973 than once to a message-body. 1975 1974 </t> 1976 1975 <t> … … 1981 1980 has a different focus for an 8bit-clean transfer protocol. In HTTP, 1982 1981 the only unsafe characteristic of message-bodies is the difficulty in 1983 determining the exact body length (<xref target="message.body.length"/>), or the desire to1984 encrypt data over a shared transport.1982 determining the exact message body length (<xref target="message.body"/>), 1983 or the desire to encrypt data over a shared transport. 1985 1984 </t> 1986 1985 <t> … … 2348 2347 In order to remain persistent, all messages on the connection &MUST; 2349 2348 have a self-defined message length (i.e., one not defined by closure 2350 of the connection), as described in <xref target="message.body .length"/>.2349 of the connection), as described in <xref target="message.body"/>. 2351 2350 </t> 2352 2351 </section> … … 2908 2907 length when no transfer-coding is being applied and the 2909 2908 payload's body length can be determined prior to being transferred. 2909 <xref target="message.body"/> describes how recipients determine the length 2910 of a message-body. 2910 2911 </t> 2911 2912 <t> 2912 2913 Any Content-Length greater than or equal to zero is a valid value. 2913 <xref target="message.body.length"/> describes how to determine the length of a message-body 2914 if a Content-Length is not given. 2915 </t> 2916 <t> 2917 Note that the meaning of this field is significantly different from 2914 </t> 2915 <t> 2916 Note that the use of this field in HTTP is significantly different from 2918 2917 the corresponding definition in MIME, where it is an optional field 2919 2918 used within the "message/external-body" content-type. … … 4873 4872 transfer encoding that may not be self delimiting); it was important 4874 4873 to straighten out exactly how message lengths are computed. (Sections 4875 <xref target="transfer.codings" format="counter"/>, <xref target="message.body .length" format="counter"/>,4874 <xref target="transfer.codings" format="counter"/>, <xref target="message.body" format="counter"/>, 4876 4875 <xref target="header.content-length" format="counter"/>, 4877 4876 see also <xref target="Part5"/>) … … 4930 4929 Remove reference to non-existent identity transfer-coding value tokens. 4931 4930 (Sections <xref format="counter" target="transfer.codings"/> and 4932 <xref format="counter" target="message.body .length"/>)4931 <xref format="counter" target="message.body"/>) 4933 4932 </t> 4934 4933 <t> -
draft-ietf-httpbis/latest/p3-payload.xml
r859 r864 27 27 <!ENTITY header-vary "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 28 28 <!ENTITY message-body "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 29 <!ENTITY message-length "<xref target='Part1' x:rel='#message.body.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">30 29 <!ENTITY header-fields "<xref target='Part1' x:rel='#header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 31 30 <!ENTITY multipart-byteranges "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
Note: See TracChangeset
for help on using the changeset viewer.