Changeset 137 for draft-ietf-httpbis/latest/p3-payload.html

Timestamp:

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

Author:

julian.reschke@…

Message:

Use consistent status reason phrases.

File:

• draft-ietf-httpbis/latest/p3-payload.html (modified) (2 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -912 +912 @@
       <p id="rfc.section.5.1.p.8">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field
          is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then
-         the server <em class="bcp14">SHOULD</em> send a 406 (not acceptable) response.
+         the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response.
       </p>
       <p id="rfc.section.5.1.p.9">A more elaborate example is</p>
@@ -963 +963 @@
       </p>
       <p id="rfc.section.5.2.p.6">If no Accept-Charset header is present, the default is that any character set is acceptable. If an Accept-Charset header is
-         present, and if the server cannot send a response which is acceptable according to the Accept-Charset header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (not acceptable) status code, though the sending of an unacceptable response is also allowed.
+         present, and if the server cannot send a response which is acceptable according to the Accept-Charset header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code, though the sending of an unacceptable response is also allowed.
       </p>
       <div id="rfc.iref.a.3"></div>