Changeset 137 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 03/01/08 16:21:04 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r136 r137 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 913 913 is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then 914 the server <em class="bcp14">SHOULD</em> send a 406 ( not acceptable) response.914 the server <em class="bcp14">SHOULD</em> send a 406 (Not Acceptable) response. 915 915 </p> 916 916 <p id="rfc.section.5.1.p.9">A more elaborate example is</p> … … 963 963 </p> 964 964 <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 965 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.965 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. 966 966 </p> 967 967 <div id="rfc.iref.a.3"></div>
Note: See TracChangeset
for help on using the changeset viewer.