Changeset 1421 for draft-ietf-httpbis

Timestamp:

Aug 31, 2011, 1:43:52 AM (8 years ago)

Author:

julian.reschke@…

Message:

rephrase 303 description (now doesn't imply GET is needed anymore) (see #310)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (7 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires March 2, 2012"; 
+       content: "Expires March 3, 2012"; 
   } 
   @bottom-right {
@@ -408 +408 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-08-30">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-08-31">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields.">
@@ -439 +439 @@
             </tr>
             <tr>
-               <td class="left">Expires: March 2, 2012</td>
+               <td class="left">Expires: March 3, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -492 +492 @@
             <tr>
                <td class="left"></td>
-               <td class="right">August 30, 2011</td>
+               <td class="right">August 31, 2011</td>
             </tr>
          </tbody>
@@ -522 +522 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on March 2, 2012.</p>
+      <p>This Internet-Draft will expire on March 3, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1752 +1752 @@
       <div id="rfc.iref.s.14"></div>
       <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
-      <p id="rfc.section.7.3.4.p.1">The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides
-         an indirect response to the original request. The user agent <em class="bcp14">MAY</em> perform a GET request on the URI in the Location field in order to obtain a representation corresponding to the response,
-         be redirected again, or end with an error status. The Location URI is not a substitute reference for the effective request
-         URI.
-      </p>
-      <p id="rfc.section.7.3.4.p.2">The 303 status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action
-         to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
+      <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.
+      </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
+         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
          in a form that can be separately identified, bookmarked, and cached independent of the original request.
       </p>
@@ -3120 +3121 @@
       </ul>
       <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>
-      <p id="rfc.section.C.18.p.1">Work-in-progress: </p>
+      <p id="rfc.section.C.18.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/310">http://tools.ietf.org/wg/httpbis/trac/ticket/310</a>&gt;: "clarify 303 redirect on HEAD"
+         </li>
+      </ul>
+      <p id="rfc.section.C.18.p.2">Work-in-progress: </p>
       <ul>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/231">http://tools.ietf.org/wg/httpbis/trac/ticket/231</a>&gt;: "Considerations for new headers"

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

@@ -1698 +1698 @@
   <iref primary="true" item="Status Codes" subitem="303 See Other" x:for-anchor=""/>
 <t>
-   The server directs the user agent to a different resource, indicated
-   by a URI in the Location header field, that provides an indirect
-   response to the original request.  The user agent &MAY; perform a GET
-   request on the URI in the Location field in order to obtain a
-   representation corresponding to the response, be redirected again,
-   or end with an error status.  The Location URI is not a substitute
-   reference for the effective request URI.
-</t>
-<t>
-   The 303 status code is generally applicable to any HTTP method.  It is
+   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 &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.
+   Note that the new URI in the Location header field is not considered
+   equivalent to the effective request URI. 
+</t>
+<t>
+   This status code is generally applicable to any HTTP method.  It is
    primarily used to allow the output of a POST action to redirect
    the user agent to a selected resource, since doing so provides the
@@ -4267 +4269 @@
 <section title="Since draft-ietf-httpbis-p2-semantics-16" anchor="changes.since.16">
 <t>
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/310"/>:
+      "clarify 303 redirect on HEAD"
+    </t>
+  </list>
+</t>
+<t>
   Work-in-progress:
   <list style="symbols">