Changeset 1964 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 01/11/12 18:46:15 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1963 r1964 656 656 Language tags are defined in <xref target="language.tags"/>. The primary purpose of 657 657 Content-Language is to allow a user to identify and differentiate 658 representations according to the user 'sown preferred language. Thus, if the658 representations according to the users' own preferred language. Thus, if the 659 659 content is intended only for a Danish-literate audience, the 660 660 appropriate field is … … 1002 1002 but it cannot expect responses to always honor them. For example, the origin 1003 1003 server might not implement proactive negotiation, or it might decide that 1004 sending a response that doesn't conform to the m is better than sending a <x:ref>4061005 (Not Acceptable)</x:ref> response.1004 sending a response that doesn't conform to the user agent's preferences is 1005 better than sending a <x:ref>406 (Not Acceptable)</x:ref> response. 1006 1006 </t> 1007 1007 <t> … … 2315 2315 <t> 2316 2316 would mean: "I prefer Danish, but will accept British English and 2317 other types of English". 2318 (see also <xref target="RFC4647" x:sec="2.3" x:fmt="of"/>) 2317 other types of English". (See also <xref target="RFC4647" x:sec="2.3" x:fmt="of"/>) 2319 2318 </t> 2320 2319 <t> … … 2513 2512 <section title="Response Status Codes" anchor="status.codes"> 2514 2513 <t> 2515 The status-code element is a 3-digit integer result code of the attempt to2516 understand and satisfy the request.2514 The status-code element is a 3-digit integer code giving the result of the 2515 attempt to understand and satisfy the request. 2517 2516 </t> 2518 2517 <t> … … 2537 2536 <list style="symbols"> 2538 2537 <t> 2539 <x:ref>1xx (Informational)</x:ref>: Request received, continuing process 2538 <x:ref>1xx (Informational)</x:ref>: The request was received, continuing 2539 process 2540 2540 </t> 2541 2541 <t> 2542 <x:ref>2xx (Successful)</x:ref>: The actionwas successfully received,2543 2542 <x:ref>2xx (Successful)</x:ref>: The request was successfully received, 2543 understood, and accepted 2544 2544 </t> 2545 2545 <t> 2546 2546 <x:ref>3xx (Redirection)</x:ref>: Further action needs to be taken in order to 2547 2547 complete the request 2548 2548 </t> 2549 2549 <t> 2550 2550 <x:ref>4xx (Client Error)</x:ref>: The request contains bad syntax or cannot 2551 2551 be fulfilled 2552 2552 </t> 2553 2553 <t> 2554 2554 <x:ref>5xx (Server Error)</x:ref>: The server failed to fulfill an apparently 2555 2555 valid request 2556 2556 </t> 2557 2557 </list> … … 2610 2610 <c>414</c> <c>URI Too Long</c> <c><xref target="status.414"/></c> 2611 2611 <c>415</c> <c>Unsupported Media Type</c> <c><xref target="status.415"/></c> 2612 <c>416</c> <c>Requested range not satisfiable</c> <c anchor="status.416">&status-416;</c>2612 <c>416</c> <c>Requested Range Not Satisfiable</c> <c anchor="status.416">&status-416;</c> 2613 2613 <c>417</c> <c>Expectation Failed</c> <c><xref target="status.417"/></c> 2614 2614 <c>426</c> <c>Upgrade Required</c> <c><xref target="status.426"/></c> … … 2746 2746 The origin server &MUST; create the resource(s) before returning the 201 status 2747 2747 code. If the action cannot be carried out immediately, the server &SHOULD; 2748 respond with <x:ref>202 (Accepted)</x:ref> response instead.2748 respond with a <x:ref>202 (Accepted)</x:ref> response instead. 2749 2749 </t> 2750 2750 <t> … … 4411 4411 <x:lt><t>Whether it is appropriate to list the field-name in the 4412 4412 <x:ref>Connection</x:ref> header field (i.e., if the header field is to 4413 be hop-by-hop ,see &header-connection;).</t></x:lt>4413 be hop-by-hop; see &header-connection;).</t></x:lt> 4414 4414 <x:lt><t>Under what conditions intermediaries are allowed to modify the header 4415 4415 field's value, insert or delete it.</t></x:lt> … … 5653 5653 <t> 5654 5654 Remove base URI setting semantics for "<x:ref>Content-Location</x:ref>" due to 5655 poor implementation support ,which was caused by too many broken servers emitting5655 poor implementation support (which was caused by too many broken servers emitting 5656 5656 bogus Content-Location header fields, and also the potentially undesirable effect 5657 of potentially breaking relative links in content-negotiated resources .5657 of potentially breaking relative links in content-negotiated resources). 5658 5658 (<xref target="header.content-location"/>) 5659 5659 </t>
Note: See TracChangeset
for help on using the changeset viewer.