Changeset 242 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

Apr 15, 2008, 8:57:31 AM (12 years ago)

Author:

julian.reschke@…

Message:

Resolve #70: replace description of 303 status with rewrite proposed by Roy Fielding in <​http://lists.w3.org/Archives/Public/ietf-http-wg/2007JulSep/0048.html>; leaving ticket open for further discussion.

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (3 diffs)

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

@@ -447 +447 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">April 10, 2008</td>
+            <td class="header right">April 15, 2008</td>
          </tr>
       </table>
@@ -1144 +1144 @@
       <div id="rfc.iref.s.13"></div>
       <h3 id="rfc.section.9.3.4"><a href="#rfc.section.9.3.4">9.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
-      <p id="rfc.section.9.3.4.p.1">The response to the request can be found under a different URI and <em class="bcp14">SHOULD</em> be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script
-         to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested
-         resource. The 303 response <em class="bcp14">MUST NOT</em> be cached, but the response to the second (redirected) request might be cacheable.
-      </p>
-      <p id="rfc.section.9.3.4.p.2">The different URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s). 
-      </p>
-      <dl class="empty">
-         <dd> <b>Note:</b> Many pre-HTTP/1.1 user agents do not understand the 303 status. When interoperability with such clients is a concern, the
-            302 status code may be used instead, since most user agents react to a 302 response as described here for 303.
-         </dd>
-      </dl>
+      <p id="rfc.section.9.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 originally requested
+         resource.
+      </p>
+      <p id="rfc.section.9.3.4.p.2">The 303 status 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>
+      <p id="rfc.section.9.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
+         transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
+         that the follow-on representation may be useful without implying that that it adequately represents the previously requested
+         resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might
+         be a useful description are outside the scope of HTTP and thus entirely determined by the resource owner(s).
+      </p>
+      <p id="rfc.section.9.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
+         the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
+      </p>
       <div id="rfc.iref.36"></div>
       <div id="rfc.iref.s.14"></div>
@@ -1776 +1783 @@
          </li>
          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61</a>&gt;: "Redirection vs. Location"
+         </li>
+         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70</a>&gt;: "Cacheability of 303 response"
          </li>
          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/76">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/76</a>&gt;: "305 Use Proxy"