Changeset 600 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 06/07/09 09:50:26 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r599 r600 32 32 <!ENTITY request-header-fields "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 33 33 <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 34 <!ENTITY method "<xref target='Part2' x:rel='#method' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">35 34 <!ENTITY status-codes "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 36 35 <!ENTITY status-100 "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1378 1377 The presence of a message-body in a request is signaled by the 1379 1378 inclusion of a Content-Length or Transfer-Encoding header field in 1380 the request's message-headers. A message-body &MUST-NOT; be included in 1381 a request if the specification of the request method (&method;) 1382 explicitly disallows an entity-body in requests. 1379 the request's message-headers. 1383 1380 When a request message contains both a message-body of non-zero 1384 1381 length and a method that does not define any semantics for that … … 4952 4949 <list style="symbols"> 4953 4950 <t> 4951 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/88"/>: 4952 "205 Bodies" (took out language that implied that there may be 4953 methods for which a request body MUST NOT be included) 4954 </t> 4955 <t> 4954 4956 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/163"/>: 4955 4957 "editorial improvements around HTTP-date"
Note: See TracChangeset
for help on using the changeset viewer.