Ignore:
Timestamp:
Jan 3, 2008, 8:21:04 AM (12 years ago)
Author:
julian.reschke@…
Message:

Use consistent status reason phrases.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r135 r137  
    12051205<t>
    12061206   A server which receives an entity-body with a transfer-coding it does
    1207    not understand &SHOULD; return 501 (Unimplemented), and close the
     1207   not understand &SHOULD; return 501 (Not Implemented), and close the
    12081208   connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0
    12091209   client.
     
    14331433   &MUST-NOT; include a message-body, even though the presence of entity-header
    14341434   fields might lead one to believe they do. All 1xx
    1435    (informational), 204 (no content), and 304 (not modified) responses
     1435   (informational), 204 (No Content), and 304 (Not Modified) responses
    14361436   &MUST-NOT; include a message-body. All other responses do include a
    14371437   message-body, although it &MAY; be of zero length.
     
    14981498   field unless the server is known to be HTTP/1.1 compliant. If a
    14991499   request contains a message-body and a Content-Length is not given,
    1500    the server &SHOULD; respond with 400 (bad request) if it cannot
    1501    determine the length of the message, or with 411 (length required) if
     1500   the server &SHOULD; respond with 400 (Bad Request) if it cannot
     1501   determine the length of the message, or with 411 (Length Required) if
    15021502   it wishes to insist on receiving a valid Content-Length.
    15031503</t>
Note: See TracChangeset for help on using the changeset viewer.