Changeset 1421 for draft-ietf-httpbis


Ignore:
Timestamp:
31/08/11 08:43:52 (10 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:
2 edited

Legend:

Unmodified
Added
Removed

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

    r1420 r1421  
    359359  }
    360360  @bottom-center {
    361        content: "Expires March 2, 2012";
     361       content: "Expires March 3, 2012";
    362362  }
    363363  @bottom-right {
    … …  
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-08-30">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-08-31">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    412412      <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.">
    … …  
    439439            </tr>
    440440            <tr>
    441                <td class="left">Expires: March 2, 2012</td>
     441               <td class="left">Expires: March 3, 2012</td>
    442442               <td class="right">HP</td>
    443443            </tr>
    … …  
    492492            <tr>
    493493               <td class="left"></td>
    494                <td class="right">August 30, 2011</td>
     494               <td class="right">August 31, 2011</td>
    495495            </tr>
    496496         </tbody>
    … …  
    522522         in progress”.
    523523      </p>
    524       <p>This Internet-Draft will expire on March 2, 2012.</p>
     524      <p>This Internet-Draft will expire on March 3, 2012.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    17521752      <div id="rfc.iref.s.14"></div>
    17531753      <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>
    1754       <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
    1755          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,
    1756          be redirected again, or end with an error status. The Location URI is not a substitute reference for the effective request
    1757          URI.
    1758       </p>
    1759       <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
    1760          to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
     1754      <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
     1755         in the Location header field, that is intended to provide an indirect response to the original request. In order to satisfy
     1756         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
     1757         as an answer to the original request. Note that the new URI in the Location header field is not considered equivalent to the
     1758         effective request URI.
     1759      </p>
     1760      <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
     1761         redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    17611762         in a form that can be separately identified, bookmarked, and cached independent of the original request.
    17621763      </p>
    … …  
    31203121      </ul>
    31213122      <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>
    3122       <p id="rfc.section.C.18.p.1">Work-in-progress: </p>
     3123      <p id="rfc.section.C.18.p.1">Closed issues: </p>
     3124      <ul>
     3125         <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"
     3126         </li>
     3127      </ul>
     3128      <p id="rfc.section.C.18.p.2">Work-in-progress: </p>
    31233129      <ul>
    31243130         <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

    r1417 r1421  
    16981698  <iref primary="true" item="Status Codes" subitem="303 See Other" x:for-anchor=""/>
    16991699<t>
    1700    The server directs the user agent to a different resource, indicated
    1701    by a URI in the Location header field, that provides an indirect
    1702    response to the original request.  The user agent &MAY; perform a GET
    1703    request on the URI in the Location field in order to obtain a
    1704    representation corresponding to the response, be redirected again,
    1705    or end with an error status.  The Location URI is not a substitute
    1706    reference for the effective request URI.
    1707 </t>
    1708 <t>
    1709    The 303 status code is generally applicable to any HTTP method.  It is
     1700   The 303 status code indicates that the server is redirecting the
     1701   user agent to a different resource, as indicated by a URI in the
     1702   Location header field, that is intended to provide an indirect
     1703   response to the original request.  In order to satisfy the original
     1704   request, a user agent &SHOULD; perform a retrieval request using the
     1705   Location URI, which may itself be redirected further, and present
     1706   the eventual result as an answer to the original request.
     1707   Note that the new URI in the Location header field is not considered
     1708   equivalent to the effective request URI.
     1709</t>
     1710<t>
     1711   This status code is generally applicable to any HTTP method.  It is
    17101712   primarily used to allow the output of a POST action to redirect
    17111713   the user agent to a selected resource, since doing so provides the
    … …  
    42674269<section title="Since draft-ietf-httpbis-p2-semantics-16" anchor="changes.since.16">
    42684270<t>
     4271  Closed issues:
     4272  <list style="symbols">
     4273    <t>
     4274      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/310"/>:
     4275      "clarify 303 redirect on HEAD"
     4276    </t>
     4277  </list>
     4278</t>
     4279<t>
    42694280  Work-in-progress:
    42704281  <list style="symbols">
Note: See TracChangeset for help on using the changeset viewer.