Ignore:
Timestamp:
Sep 1, 2011, 3:45:25 AM (8 years ago)
Author:
julian.reschke@…
Message:

Point out that retrieval in HTTP is GET or HEAD (see [1421] and #310)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1428 r1429  
    17851785      <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
    17861786         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, which may itself be redirected further, and present the eventual result
    1788          as an answer to the original request. Note that the new URI in the Location header field is not considered equivalent to the
    1789          effective request URI.
     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 itself
     1788         be redirected further, and present the eventual result as an answer to the original request. Note that the new URI in the
     1789         Location header field is not considered equivalent to the effective request URI.
    17901790      </p>
    17911791      <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
Note: See TracChangeset for help on using the changeset viewer.