Changeset 2056
- Timestamp:
- 20/12/12 09:33:38 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2055 r2056 449 449 } 450 450 @bottom-center { 451 content: "Expires June 19, 2013";451 content: "Expires June 23, 2013"; 452 452 } 453 453 @bottom-right { … … 495 495 <meta name="dct.creator" content="Reschke, J. F."> 496 496 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 497 <meta name="dct.issued" scheme="ISO8601" content="2012-12- 16">497 <meta name="dct.issued" scheme="ISO8601" content="2012-12-20"> 498 498 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 499 499 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 523 523 <tr> 524 524 <td class="left">Intended status: Standards Track</td> 525 <td class="right">December 16, 2012</td>525 <td class="right">December 20, 2012</td> 526 526 </tr> 527 527 <tr> 528 <td class="left">Expires: June 19, 2013</td>528 <td class="left">Expires: June 23, 2013</td> 529 529 <td class="right"></td> 530 530 </tr> … … 554 554 in progress”. 555 555 </p> 556 <p>This Internet-Draft will expire on June 19, 2013.</p>556 <p>This Internet-Draft will expire on June 23, 2013.</p> 557 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 558 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2469 2469 <div id="rfc.iref.72"></div> 2470 2470 <div id="rfc.iref.s.4"></div> 2471 <p id="rfc.section.6.4.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.</p> 2471 <p id="rfc.section.6.4.p.1">The <dfn>3xx (Redirection)</dfn> class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. 2472 </p> 2472 2473 <p id="rfc.section.6.4.p.2">There are several types of redirects: </p> 2473 2474 <ol> … … 2512 2513 <div id="rfc.iref.73"></div> 2513 2514 <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 2514 <p id="rfc.section.6.4.1.p.1">The target resource has more than one representation, each with its own specific location, and reactive negotiation information 2515 (<a href="#content.negotiation" title="Content Negotiation">Section 3.4</a>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that 2516 location. 2517 </p> 2518 <p id="rfc.section.6.4.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can 2519 choose the one most appropriate. Depending upon the format and the capabilities of the user agent, selection of the most appropriate 2520 choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection. 2521 </p> 2522 <p id="rfc.section.6.4.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. 2515 <p id="rfc.section.6.4.1.p.1">The <dfn>300 (Multiple Choices)</dfn> status code indicates that the target resource has more than one representation, each with its own more specific identifier, 2516 and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation 2517 by redirecting its request to one or more of those identifiers. In other words, the server desires that the user agent engage 2518 in reactive negotiation to select the most appropriate representation(s) for its needs (<a href="#content.negotiation" title="Content Negotiation">Section 3.4</a>). 2519 </p> 2520 <p id="rfc.section.6.4.1.p.2">For request methods other than HEAD, the server <em class="bcp14">SHOULD</em> generate a payload in the 300 response containing a list of representation metadata and URI reference(s) from which the user 2521 or user agent can choose the one most preferred. The user agent <em class="bcp14">MAY</em> make a selection from that list automatically, depending upon the list format, but this specification does not define a standard 2522 for such automatic selection. 2523 </p> 2524 <p id="rfc.section.6.4.1.p.3">If the server has a preferred choice, the server <em class="bcp14">SHOULD</em> generate a <a href="#header.location" class="smpl">Location</a> header field containing a preferred choice's URI reference. The user agent <em class="bcp14">MAY</em> use the Location field value for automatic redirection. 2523 2525 </p> 2524 2526 <p id="rfc.section.6.4.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 300 responses. … … 2526 2528 <div id="rfc.iref.73"></div> 2527 2529 <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h3> 2528 <p id="rfc.section.6.4.2.p.1">The target resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the enclosed URIs. Clients with link editing capabilities ought to automatically re-link references to the effective2529 request URI to one or more of the new references sent by the server, where possible.2530 </p>2531 < p id="rfc.section.6.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses.2532 < /p>2533 <p id="rfc.section.6.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext notewith a hyperlink to the new URI(s).2534 </p> 2535 <div class="note" id="rfc.section.6.4.2.p. 4">2530 <p id="rfc.section.6.4.2.p.1">The <dfn>301 (Moved Permanently)</dfn> status code indicates that the target resource has been assigned a new permanent URI and any future references to this resource 2531 ought to use one of the enclosed URIs. Clients with link editing capabilities ought to automatically re-link references to 2532 the effective request URI to one or more of the new references sent by the server, where possible. 2533 </p> 2534 <p id="rfc.section.6.4.2.p.2">The server <em class="bcp14">SHOULD</em> generate a <a href="#header.location" class="smpl">Location</a> header field in the response containing a preferred URI reference for the new permanent URI. The user agent <em class="bcp14">MAY</em> use the Location field value for automatic redirection. The server's response payload usually contains a short hypertext note 2535 with a hyperlink to the new URI(s). 2536 </p> 2537 <div class="note" id="rfc.section.6.4.2.p.3"> 2536 2538 <p> <b>Note:</b> For historic reasons, user agents <em class="bcp14">MAY</em> change the request method from POST to GET for the subsequent request. If this behavior is undesired, status code <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> can be used instead. 2537 2539 </p> 2538 2540 </div> 2541 <p id="rfc.section.6.4.2.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses. 2542 </p> 2539 2543 <div id="rfc.iref.73"></div> 2540 2544 <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a> <a id="status.302" href="#status.302">302 Found</a></h3> 2541 <p id="rfc.section.6.4.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests. 2542 </p> 2543 <p id="rfc.section.6.4.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s). 2545 <p id="rfc.section.6.4.3.p.1">The <dfn>302 (Found)</dfn> status code indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered 2546 on occasion, the client ought to continue to use the effective request URI for future requests. 2547 </p> 2548 <p id="rfc.section.6.4.3.p.2">The server <em class="bcp14">SHOULD</em> generate a <a href="#header.location" class="smpl">Location</a> header field in the response containing a URI reference for the different URI. The user agent <em class="bcp14">MAY</em> use the Location field value for automatic redirection. The server's response payload usually contains a short hypertext note 2549 with a hyperlink to the different URI(s). 2544 2550 </p> 2545 2551 <div class="note" id="rfc.section.6.4.3.p.3"> … … 2549 2555 <div id="rfc.iref.73"></div> 2550 2556 <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3> 2551 <p id="rfc.section.6.4.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 2552 in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request, 2553 a user agent <em class="bcp14">SHOULD</em> perform a retrieval request using the Location URI (a GET or HEAD request if using HTTP), which can itself be redirected further, 2554 and present the eventual result as an answer to the original request. Note that the new URI in the Location header field is 2555 not considered equivalent to the effective request URI. 2556 </p> 2557 <p id="rfc.section.6.4.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 2558 redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response 2559 in a form that can be separately identified, bookmarked, and cached independent of the original request. 2557 <p id="rfc.section.6.4.4.p.1">The <dfn>303 (See Other)</dfn> status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request, 2558 a user agent ought to perform a retrieval request using the Location URI (a GET or HEAD request if using HTTP), which can 2559 itself be redirected further, and present the eventual result as an answer to the original request. Note that the new URI 2560 in the Location header field is not considered equivalent to the effective request URI. 2561 </p> 2562 <p id="rfc.section.6.4.4.p.2">This status code is applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect the 2563 user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form that 2564 can be separately identified, bookmarked, and cached independent of the original request. 2560 2565 </p> 2561 2566 <p id="rfc.section.6.4.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 … … 2565 2570 and thus entirely determined by the URI owner(s). 2566 2571 </p> 2567 <p id="rfc.section.6.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the <a href="#header.location" class="smpl">Location</a> URI. 2572 <p id="rfc.section.6.4.4.p.4">Except for responses to a HEAD request, the representation of a 303 response ought to contain a short hypertext note with 2573 a hyperlink to the same URI reference provided in the <a href="#header.location" class="smpl">Location</a> header field. 2568 2574 </p> 2569 2575 <div id="rfc.iref.73"></div> 2570 2576 <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 2571 <p id="rfc.section.6.4.5.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix C</a>), and is now deprecated.2577 <p id="rfc.section.6.4.5.p.1">The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated (<a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix C</a>). 2572 2578 </p> 2573 2579 <div id="rfc.iref.73"></div> 2574 2580 <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a> <a id="status.306" href="#status.306">306 (Unused)</a></h3> 2575 <p id="rfc.section.6.4.6.p.1">The 306 status code was used in a previous version of thespecification, is no longer used, and the code is reserved.</p>2581 <p id="rfc.section.6.4.6.p.1">The 306 status code was defined in a previous version of this specification, is no longer used, and the code is reserved.</p> 2576 2582 <div id="rfc.iref.73"></div> 2577 2583 <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h3> 2578 <p id="rfc.section.6.4.7.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests. 2579 </p> 2580 <p id="rfc.section.6.4.7.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s). 2584 <p id="rfc.section.6.4.7.p.1">The <dfn>307 (Temporary Redirect)</dfn> status code indicates that the target resource resides temporarily under a different URI and the user agent <em class="bcp14">MUST NOT</em> change the request method if it performs an automatic redirection to that URI. Since the redirection can change over time, 2585 the client ought to continue using the original effective request URI for future requests. 2586 </p> 2587 <p id="rfc.section.6.4.7.p.2">The server <em class="bcp14">SHOULD</em> generate a <a href="#header.location" class="smpl">Location</a> header field in the response containing a URI reference for the different URI. The user agent <em class="bcp14">MAY</em> use the Location field value for automatic redirection. The server's response payload usually contains a short hypertext note 2588 with a hyperlink to the different URI(s). 2581 2589 </p> 2582 2590 <div class="note" id="rfc.section.6.4.7.p.3"> 2583 <p> <b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow rewriting the request method from POST to GET. This specification defines no equivalent counterpart2591 <p> <b>Note:</b> This status code is similar to <a href="#status.302" class="smpl">302 (Found)</a>, except that it does not allow changing the request method from POST to GET. This specification defines no equivalent counterpart 2584 2592 for <a href="#status.301" class="smpl">301 (Moved 2585 2593 Permanently)</a> (<a href="#status-308" id="rfc.xref.status-308.1"><cite title="The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)">[status-308]</cite></a>, however, defines the status code 308 (Permanent Redirect) for this purpose). … … 2589 2597 <div id="rfc.iref.73"></div> 2590 2598 <div id="rfc.iref.s.5"></div> 2591 <p id="rfc.section.6.5.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD 2592 request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition. 2599 <p id="rfc.section.6.5.p.1">The <dfn>4xx (Client Error)</dfn> class of status code indicates that the client seems to have erred. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition. 2593 2600 These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user. 2594 2601 </p> … … 2598 2605 <div id="rfc.iref.74"></div> 2599 2606 <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a> <a id="status.402" href="#status.402">402 Payment Required</a></h3> 2600 <p id="rfc.section.6.5.2.p.1">This code is reserved for future use.</p> 2607 <p id="rfc.section.6.5.2.p.1">The <dfn>402 (Payment Required)</dfn> status code is reserved for future use. 2608 </p> 2601 2609 <div id="rfc.iref.74"></div> 2602 2610 <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2055 r2056 2826 2826 <iref primary="true" item="Status Codes Classes" subitem="3xx Redirection" x:for-anchor=""/> 2827 2827 <t> 2828 This class of status code indicates that further action needs to be 2829 taken by the user agent in order to fulfill the request. 2828 The <x:dfn>3xx (Redirection)</x:dfn> class of status code indicates that 2829 further action needs to be taken by the user agent in order to fulfill the 2830 request. 2830 2831 </t> 2831 2832 <t> … … 2909 2910 <x:anchor-alias value="300 (Multiple Choices)"/> 2910 2911 <t> 2911 The target resource has more than one 2912 representation, each with its own specific location, and reactive 2913 negotiation information (&content-negotiation;) is being provided so that 2914 the user (or user agent) can select a preferred representation by 2915 redirecting its request to that location. 2916 </t> 2917 <t> 2918 Unless it was a HEAD request, the response &SHOULD; include a representation 2919 containing a list of representation metadata and location(s) from 2920 which the user or user agent can choose the one most appropriate. Depending 2921 upon the format and the capabilities of 2922 the user agent, selection of the most appropriate choice &MAY; be 2923 performed automatically. However, this specification does not define 2924 any standard for such automatic selection. 2925 </t> 2926 <t> 2927 If the server has a preferred choice of representation, it &SHOULD; 2928 include the specific URI for that representation in the <x:ref>Location</x:ref> 2929 field; user agents &MAY; use the Location field value for automatic 2930 redirection. 2912 The <x:dfn>300 (Multiple Choices)</x:dfn> status code indicates that the 2913 target resource has more than one representation, each with its own more 2914 specific identifier, and information about the alternatives is being 2915 provided so that the user (or user agent) can select a preferred 2916 representation by redirecting its request to one or more of those 2917 identifiers. In other words, the server desires that the user agent engage 2918 in reactive negotiation to select the most appropriate representation(s) 2919 for its needs (&content-negotiation;). 2920 </t> 2921 <t> 2922 For request methods other than HEAD, the server &SHOULD; generate a payload 2923 in the 300 response containing a list of representation metadata and URI 2924 reference(s) from which the user or user agent can choose the one most 2925 preferred. The user agent &MAY; make a selection from that list 2926 automatically, depending upon the list format, but this specification does 2927 not define a standard for such automatic selection. 2928 </t> 2929 <t> 2930 If the server has a preferred choice, the server &SHOULD; generate a 2931 <x:ref>Location</x:ref> header field containing a preferred choice's URI 2932 reference. The user agent &MAY; use the Location field value for automatic 2933 redirection. 2931 2934 </t> 2932 2935 <t> … … 2942 2945 <x:anchor-alias value="301 (Moved Permanently)"/> 2943 2946 <t> 2944 The target resource has been assigned a new permanent URI and any 2945 future references to this resource &SHOULD; use one of the enclosed 2946 URIs. Clients with link editing capabilities ought to automatically 2947 re-link references to the effective request URI to one or more of the new 2948 references sent by the server, where possible. 2949 </t> 2950 <t> 2951 Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 2952 freshness for 301 responses. 2953 </t> 2954 <t> 2955 The new permanent URI &SHOULD; be given by the <x:ref>Location</x:ref> field 2956 in the response. A response payload can contain a short hypertext note with a 2957 hyperlink to the new URI(s). 2947 The <x:dfn>301 (Moved Permanently)</x:dfn> status code indicates that the 2948 target resource has been assigned a new permanent URI and any future 2949 references to this resource ought to use one of the enclosed URIs. Clients 2950 with link editing capabilities ought to automatically re-link references to 2951 the effective request URI to one or more of the new references sent by the 2952 server, where possible. 2953 </t> 2954 <t> 2955 The server &SHOULD; generate a <x:ref>Location</x:ref> header field in the 2956 response containing a preferred URI reference for the new permanent URI. 2957 The user agent &MAY; use the Location field value for automatic redirection. 2958 The server's response payload usually contains a short hypertext note with 2959 a hyperlink to the new URI(s). 2958 2960 </t> 2959 2961 <x:note> … … 2965 2967 </t> 2966 2968 </x:note> 2969 <t> 2970 Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 2971 freshness for 301 responses. 2972 </t> 2967 2973 </section> 2968 2974 … … 2972 2978 <x:anchor-alias value="302 (Found)"/> 2973 2979 <t> 2974 The target resource resides temporarily under a different URI. 2975 Since the redirection might be altered on occasion, the client &SHOULD; 2976 continue to use the effective request URI for future requests. 2977 </t> 2978 <t> 2979 The temporary URI &SHOULD; be given by the <x:ref>Location</x:ref> field in 2980 the response. A response payload can contain a short hypertext note with a 2981 hyperlink to the new URI(s). 2980 The <x:dfn>302 (Found)</x:dfn> status code indicates that the target 2981 resource resides temporarily under a different URI. Since the redirection 2982 might be altered on occasion, the client ought to continue to use the 2983 effective request URI for future requests. 2984 </t> 2985 <t> 2986 The server &SHOULD; generate a <x:ref>Location</x:ref> header field in the 2987 response containing a URI reference for the different URI. 2988 The user agent &MAY; use the Location field value for automatic redirection. 2989 The server's response payload usually contains a short hypertext note with 2990 a hyperlink to the different URI(s). 2982 2991 </t> 2983 2992 <x:note> … … 2995 3004 <x:anchor-alias value="303 (See Other)"/> 2996 3005 <t> 2997 The 303 status code indicates that the server is redirecting the 2998 user agent to a different resource, as indicated by a URI in the 2999 <x:ref>Location</x:ref> header field, that is intended to provide an indirect 3000 response to the original request. In order to satisfy the original 3001 request, a user agent &SHOULD; perform a retrieval request using the 3002 Location URI (a GET or HEAD request if using HTTP), which 3003 can itself be redirected further, and present the eventual result as an 3004 answer to the original request. 3005 Note that the new URI in the Location header field is not considered 3006 equivalent to the effective request URI. 3007 </t> 3008 <t> 3009 This status code is generally applicable to any HTTP method. It is 3006 The <x:dfn>303 (See Other)</x:dfn> status code indicates that the server is 3007 redirecting the user agent to a different resource, as indicated by a URI 3008 in the <x:ref>Location</x:ref> header field, that is intended to provide an 3009 indirect response to the original request. In order to satisfy the original 3010 request, a user agent ought to perform a retrieval request using the 3011 Location URI (a GET or HEAD request if using HTTP), which can itself be 3012 redirected further, and present the eventual result as an answer to the 3013 original request. Note that the new URI in the Location header field is not 3014 considered equivalent to the effective request URI. 3015 </t> 3016 <t> 3017 This status code is applicable to any HTTP method. It is 3010 3018 primarily used to allow the output of a POST action to redirect 3011 3019 the user agent to a selected resource, since doing so provides the … … 3028 3036 <t> 3029 3037 Except for responses to a HEAD request, the representation of a 303 3030 response &SHOULD; contain a short hypertext note with a hyperlink3031 to the <x:ref>Location</x:ref> URI.3038 response ought to contain a short hypertext note with a hyperlink to the 3039 same URI reference provided in the <x:ref>Location</x:ref> header field. 3032 3040 </t> 3033 3041 </section> … … 3037 3045 <x:anchor-alias value="305 (Use Proxy)"/> 3038 3046 <t> 3039 The 305 status code was defined in a previous version of this specification 3040 (see <xref target="changes.from.rfc.2616"/>), and is now deprecated. 3047 The <x:dfn>305 (Use Proxy)</x:dfn> status code was defined in a previous 3048 version of this specification and is now deprecated 3049 (<xref target="changes.from.rfc.2616"/>). 3041 3050 </t> 3042 3051 </section> … … 3045 3054 <iref primary="true" item="306 (Unused) (status code)" x:for-anchor=""/> 3046 3055 <t> 3047 The 306 status code was used in a previous version of the3056 The 306 status code was defined in a previous version of this 3048 3057 specification, is no longer used, and the code is reserved. 3049 3058 </t> … … 3055 3064 <x:anchor-alias value="307 (Temporary Redirect)"/> 3056 3065 <t> 3057 The target resource resides temporarily under a different URI. 3058 Since the redirection can change over time, the client &SHOULD; 3059 continue to use the effective request URI for future requests. 3060 </t> 3061 <t> 3062 The temporary URI &SHOULD; be given by the <x:ref>Location</x:ref> field in 3063 the response. A response payload can contain a short hypertext note with a 3064 hyperlink to the new URI(s). 3066 The <x:dfn>307 (Temporary Redirect)</x:dfn> status code indicates that the 3067 target resource resides temporarily under a different URI and the 3068 user agent &MUST-NOT; change the request method if it performs an automatic 3069 redirection to that URI. 3070 Since the redirection can change over time, the client ought to continue 3071 using the original effective request URI for future requests. 3072 </t> 3073 <t> 3074 The server &SHOULD; generate a <x:ref>Location</x:ref> header field in the 3075 response containing a URI reference for the different URI. 3076 The user agent &MAY; use the Location field value for automatic redirection. 3077 The server's response payload usually contains a short hypertext note with 3078 a hyperlink to the different URI(s). 3065 3079 </t> 3066 3080 <x:note> 3067 3081 <t> 3068 3082 &Note; This status code is similar to <x:ref>302 (Found)</x:ref>, except 3069 that it does not allow rewriting the request method from POST to GET. This3083 that it does not allow changing the request method from POST to GET. This 3070 3084 specification defines no equivalent counterpart for <x:ref>301 (Moved 3071 3085 Permanently)</x:ref> (<xref target="status-308"/>, … … 3082 3096 <iref primary="true" item="Status Codes Classes" subitem="4xx Client Error" x:for-anchor=""/> 3083 3097 <t> 3084 The 4xx class of status code is intended for cases in which the3085 client seems to have erred. Except when responding to a HEAD request,3086 the server &SHOULD; include a representation containing an explanation of the3087 error situation, and whether it is a temporary or permanent3088 condition. These status codes are applicable to any request method.3089 User agents&SHOULD; display any included representation to the user.3098 The <x:dfn>4xx (Client Error)</x:dfn> class of status code indicates that 3099 the client seems to have erred. Except when responding to a HEAD request, 3100 the server &SHOULD; send a representation containing an explanation of 3101 the error situation, and whether it is a temporary or permanent condition. 3102 These status codes are applicable to any request method. User agents 3103 &SHOULD; display any included representation to the user. 3090 3104 </t> 3091 3105 … … 3101 3115 <section title="402 Payment Required" anchor="status.402"> 3102 3116 <iref primary="true" item="402 Payment Required (status code)" x:for-anchor=""/> 3103 <t> 3104 This code is reserved for future use. 3117 <x:anchor-alias value="402 (Payment Required)"/> 3118 <t> 3119 The <x:dfn>402 (Payment Required)</x:dfn> status code is reserved for 3120 future use. 3105 3121 </t> 3106 3122 </section>
Note: See TracChangeset
for help on using the changeset viewer.