Ignore:
Timestamp:
Jul 21, 2009, 4:28:41 AM (10 years ago)
Author:
julian.reschke@…
Message:

Resolve #140: rephrase note so that it becomes clear that the described change already happened in RFC2616, also add 303/307 to the "changes from RFC2068" section (closes #140)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r609 r614  
    13371337<x:note>
    13381338  <t>
    1339     <x:h>Note:</x:h> <xref target="RFC1945"/> and <xref target="RFC2068"/> specify that the client is not allowed
    1340     to change the method on the redirected request.  However, most
    1341     existing user agent implementations treat 302 as if it were a 303
    1342     response, performing a GET on the Location field-value regardless
    1343     of the original request method. The status codes 303 and 307 have
    1344     been added for servers that wish to make unambiguously clear which
    1345     kind of reaction is expected of the client.
     1339    <x:h>Note:</x:h> HTTP/1.0 (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>)
     1340    and the first version of HTTP/1.1 (<xref target="RFC2068" x:fmt="," x:sec ="10.3.3"/>)
     1341    specify that the client is not allowed to change the method on the
     1342    redirected request.  However, most existing user agent implementations
     1343    treat 302 as if it were a 303 response, performing a GET on the Location
     1344    field-value regardless of the original request method. Therefore, a
     1345    previous version of this specification
     1346    (<xref target="RFC2616" x:fmt="," x:sec="10.3.3"/>) has added the
     1347    status codes
     1348    <xref target="status.303" format="none">303</xref> and
     1349    <xref target="status.307" format="none">307</xref> for servers that wish
     1350    to make unambiguously clear which kind of reaction is expected of the
     1351    client.
    13461352  </t>
    13471353</x:note>
     
    31413147</t>
    31423148<t>
     3149   303 (See Also) and 307 (Temporary Redirect) added to address user agent
     3150   failure to implement status code 302 properly.
     3151   (Section <xref target="status.303" format="counter"/> and <xref target="status.307" format="counter"/>)
     3152</t>
     3153<t>
    31433154   Rewrite of message transmission requirements to make it much harder
    31443155   for implementors to get it wrong, as the consequences of errors here
     
    36053616<section title="Since draft-ietf-httpbis-p2-semantics-07" anchor="changes.since.07">
    36063617<t>
    3607   None.
     3618  Closed issues:
     3619  <list style="symbols">
     3620    <t>
     3621      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/140"/>:
     3622      "update note citing RFC 1945 and 2068"
     3623    </t>
     3624  </list>
    36083625</t>
    36093626</section>
Note: See TracChangeset for help on using the changeset viewer.