Changeset 924 for draft-ietf-httpbis/latest
- Timestamp:
- 24/07/10 13:56:20 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r921 r924 616 616 <t> 617 617 The HTTP Status Code Registry defines the name space for the Status-Code 618 token in the Status line of an HTTP response.618 token in the Status-Line of an HTTP response. 619 619 </t> 620 620 <t> … … 695 695 <t>If the response status code is 200 or 203 and the request method was GET, 696 696 the response is a representation of the resource at the Effective Request URI.</t> 697 <t>If the response status is 204, 206, or 304 and the request method was GET697 <t>If the response status code is 204, 206, or 304 and the request method was GET 698 698 or HEAD, the response is a partial representation of the resource at the 699 699 Effective Request URI (see &caching-combining-headers;).</t> … … 929 929 The action performed by the POST method might not result in a 930 930 resource that can be identified by a URI. In this case, either 200 931 (OK) or 204 (No Content) is the appropriate response status ,931 (OK) or 204 (No Content) is the appropriate response status code, 932 932 depending on whether or not the response includes a representation that 933 933 describes the result. … … 985 985 responses for the Effective Request URI, those stored responses 986 986 &SHOULD; be marked as stale if the response to the PUT request 987 is a success status. Responses to the PUT method are not cacheable. 987 has a success status code. Responses to the PUT method are 988 not cacheable. 988 989 </t> 989 990 <t> … … 1267 1268 header fields refer to the requested resource and its current 1268 1269 representation, respectively, after the requested action. 1269 For example, if a 204 status is received in response to a PUT1270 For example, if a 204 status code is received in response to a PUT 1270 1271 and the response contains an ETag header field, then the value of 1271 1272 that field is the current entity-tag for the representation that … … 1459 1460 </t> 1460 1461 <t> 1461 The 303 status is generally applicable to any HTTP method. It is1462 The 303 status code is generally applicable to any HTTP method. It is 1462 1463 primarily used to allow the output of a POST action to redirect 1463 1464 the user agent to a selected resource, since doing so provides the … … 1501 1502 <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/> 1502 1503 <t> 1503 The 305 status was defined in a previous version of this specification1504 The 305 status code was defined in a previous version of this specification 1504 1505 (see <xref target="changes.from.rfc.2616"/>), and is now deprecated. 1505 1506 </t> … … 1528 1529 response &SHOULD; contain a short hypertext note with a hyperlink to 1529 1530 the new URI(s) , since many pre-HTTP/1.1 user agents do not 1530 understand the 307 status . Therefore, the note &SHOULD; contain the1531 understand the 307 status code. Therefore, the note &SHOULD; contain the 1531 1532 information necessary for a user to repeat the original request on 1532 1533 the new URI. … … 1992 1993 A server that does not understand or is unable to comply with any of 1993 1994 the expectation values in the Expect field of a request &MUST; respond 1994 with appropriate error status . The server &MUST; respond with a 4171995 (Expectation Failed) status if any of the expectations cannot be met1995 with appropriate error status code. The server &MUST; respond with a 417 1996 (Expectation Failed) status code if any of the expectations cannot be met 1996 1997 or, if there are other problems with the request, some other 4xx 1997 status .1998 status code. 1998 1999 </t> 1999 2000 <t> … … 2001 2002 future extensions. If a server receives a request containing an 2002 2003 Expect field that includes an expectation-extension that it does not 2003 support, it &MUST; respond with a 417 (Expectation Failed) status .2004 support, it &MUST; respond with a 417 (Expectation Failed) status code. 2004 2005 </t> 2005 2006 <t> … … 2010 2011 <t> 2011 2012 The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy &MUST; 2012 return a 417 (Expectation Failed) status if it receives a request2013 return a 417 (Expectation Failed) status code if it receives a request 2013 2014 with an expectation that it cannot meet. However, the Expect 2014 2015 request-header itself is end-to-end; it &MUST; be forwarded if the … … 2020 2021 </t> 2021 2022 <t> 2022 See &use100; for the use of the 100 (Continue) status .2023 See &use100; for the use of the 100 (Continue) status code. 2023 2024 </t> 2024 2025 </section>
Note: See TracChangeset
for help on using the changeset viewer.