Changeset 137 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

03/01/08 16:21:04 (13 years ago)

Author:

julian.reschke@…

Message:

Use consistent status reason phrases.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1205 +1205 @@
 <t>
    A server which receives an entity-body with a transfer-coding it does
-   not understand &SHOULD; return 501 (Unimplemented), and close the
+   not understand &SHOULD; return 501 (Not Implemented), and close the
    connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0
    client.
@@ -1433 +1433 @@
    &MUST-NOT; include a message-body, even though the presence of entity-header
    fields might lead one to believe they do. All 1xx
-   (informational), 204 (no content), and 304 (not modified) responses
+   (informational), 204 (No Content), and 304 (Not Modified) responses
    &MUST-NOT; include a message-body. All other responses do include a
    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
    request contains a message-body and a Content-Length is not given,
-   the server &SHOULD; respond with 400 (bad request) if it cannot
-   determine the length of the message, or with 411 (length required) if
+   the server &SHOULD; respond with 400 (Bad Request) if it cannot
+   determine the length of the message, or with 411 (Length Required) if
    it wishes to insist on receiving a valid Content-Length.
 </t>