Changeset 137 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 03/01/08 16:21:04 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r135 r137 1205 1205 <t> 1206 1206 A server which receives an entity-body with a transfer-coding it does 1207 not understand &SHOULD; return 501 ( Unimplemented), and close the1207 not understand &SHOULD; return 501 (Not Implemented), and close the 1208 1208 connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0 1209 1209 client. … … 1433 1433 &MUST-NOT; include a message-body, even though the presence of entity-header 1434 1434 fields might lead one to believe they do. All 1xx 1435 (informational), 204 ( no content), and 304 (not modified) responses1435 (informational), 204 (No Content), and 304 (Not Modified) responses 1436 1436 &MUST-NOT; include a message-body. All other responses do include a 1437 1437 message-body, although it &MAY; be of zero length. … … 1498 1498 field unless the server is known to be HTTP/1.1 compliant. If a 1499 1499 request contains a message-body and a Content-Length is not given, 1500 the server &SHOULD; respond with 400 ( bad request) if it cannot1501 determine the length of the message, or with 411 ( length required) if1500 the server &SHOULD; respond with 400 (Bad Request) if it cannot 1501 determine the length of the message, or with 411 (Length Required) if 1502 1502 it wishes to insist on receiving a valid Content-Length. 1503 1503 </t>
Note: See TracChangeset
for help on using the changeset viewer.