Changeset 242 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 15/04/08 15:57:31 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r241 r242 447 447 <tr> 448 448 <td class="header left"></td> 449 <td class="header right">April 1 0, 2008</td>449 <td class="header right">April 15, 2008</td> 450 450 </tr> 451 451 </table> … … 1144 1144 <div id="rfc.iref.s.13"></div> 1145 1145 <h3 id="rfc.section.9.3.4"><a href="#rfc.section.9.3.4">9.3.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3> 1146 <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 1147 to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested 1148 resource. The 303 response <em class="bcp14">MUST NOT</em> be cached, but the response to the second (redirected) request might be cacheable. 1149 </p> 1150 <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). 1151 </p> 1152 <dl class="empty"> 1153 <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 1154 302 status code may be used instead, since most user agents react to a 302 response as described here for 303. 1155 </dd> 1156 </dl> 1146 <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 1147 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, 1148 be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested 1149 resource. 1150 </p> 1151 <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 1152 the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form 1153 that can be separately identified, bookmarked, and cached independent of the original request. 1154 </p> 1155 <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 1156 transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such 1157 that the follow-on representation may be useful without implying that that it adequately represents the previously requested 1158 resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might 1159 be a useful description are outside the scope of HTTP and thus entirely determined by the resource owner(s). 1160 </p> 1161 <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, 1162 the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI. 1163 </p> 1157 1164 <div id="rfc.iref.36"></div> 1158 1165 <div id="rfc.iref.s.14"></div> … … 1776 1783 </li> 1777 1784 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61</a>>: "Redirection vs. Location" 1785 </li> 1786 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70</a>>: "Cacheability of 303 response" 1778 1787 </li> 1779 1788 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/76">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/76</a>>: "305 Use Proxy"
Note: See TracChangeset
for help on using the changeset viewer.