Changeset 1429

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)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (1 diff)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -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
          in the Location header field, that is intended to provide an indirect response to the original request. In order to satisfy
-         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
-         as an answer to the original request. Note that the new URI in the Location header field is not considered equivalent to the
-         effective request URI.
+         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
+         be redirected further, and present the eventual result as an answer to the original request. Note that the new URI in the
+         Location header field is not considered equivalent to the effective request URI.
       </p>
       <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

@@ -1751 +1751 @@
    response to the original request.  In order to satisfy the original
    request, a user agent &SHOULD; perform a retrieval request using the
-   Location URI, which may itself be redirected further, and present
-   the eventual result as an answer to the original request.
+   Location URI (in HTTP, a GET, unless the original method was HEAD), which
+   may itself be redirected further, and present the eventual result as an
+   answer to the original request.
    Note that the new URI in the Location header field is not considered
    equivalent to the effective request URI.