Changeset 1430
- Timestamp:
- 01/09/11 22:34:24 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1429 r1430 1785 1785 <p id="rfc.section.7.3.4.p.1">The 303 status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI 1786 1786 in the Location header field, that is intended to provide an indirect response to the original request. In order to satisfy 1787 the original request, a user agent <em class="bcp14">SHOULD</em> perform a retrieval request using the Location URI ( in HTTP, a GET, unless the original method was HEAD), which may itself1788 be redirected further, and present the eventual result as an answer to the original request. Note that the new URI in the1789 Location header field isnot considered equivalent to the effective request URI.1787 the original request, a user agent <em class="bcp14">SHOULD</em> perform a retrieval request using the Location URI (a GET or HEAD request if using HTTP), which may itself be redirected further, 1788 and present the eventual result as an answer to the original request. Note that the new URI in the Location header field is 1789 not considered equivalent to the effective request URI. 1790 1790 </p> 1791 1791 <p id="rfc.section.7.3.4.p.2">This status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to -
draft-ietf-httpbis/latest/p2-semantics.xml
r1429 r1430 1751 1751 response to the original request. In order to satisfy the original 1752 1752 request, a user agent &SHOULD; perform a retrieval request using the 1753 Location URI ( in HTTP, a GET, unless the original method was HEAD), which1753 Location URI (a GET or HEAD request if using HTTP), which 1754 1754 may itself be redirected further, and present the eventual result as an 1755 1755 answer to the original request.
Note: See TracChangeset
for help on using the changeset viewer.