Ignore:
Timestamp:
14/09/13 19:57:05 (7 years ago)
Author:
fielding@…
Message:

strengthen response requirements on PUT when allowed for the target resource; addresses #475

File:
1 edited

Legend:

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

    r2393 r2395  
    14331433   target resource does have a current representation and that representation is
    14341434   successfully modified in accordance with the state of the enclosed
    1435    representation, then either a <x:ref>200 (OK)</x:ref> or <x:ref>204 (No Content)</x:ref>
    1436    response &SHOULD; be sent to indicate successful completion of the request.
     1435   representation, then the origin server &MUST; send either a
     1436   <x:ref>200 (OK)</x:ref> or a <x:ref>204 (No Content)</x:ref> response to
     1437   indicate successful completion of the request.
    14371438</t>
    14381439<t>
     
    15191520</t>
    15201521<t>
    1521    A PUT request applied to the target resource &MAY; have side-effects
     1522   A PUT request applied to the target resource can have side-effects
    15221523   on other resources.  For example, an article might have a URI for
    15231524   identifying "the current version" (a resource) that is separate
     
    15301531</t>
    15311532<t>
    1532    An origin server &SHOULD; reject any PUT request that contains a
     1533   An origin server that allows PUT on a given target resource &MUST; send a
     1534   <x:ref>400 (Bad Request)</x:ref> response to a PUT request that contains a
    15331535   <x:ref>Content-Range</x:ref> header field (&header-content-range;), since
    1534    it might be misinterpreted as partial content (or might be partial content
    1535    that is being mistakenly PUT as a full representation).  Partial content
    1536    updates are possible by targeting a separately identified resource with
    1537    state that overlaps a portion of the larger resource, or by using a
    1538    different method that has been specifically defined for partial
     1536   the payload is likely to be partial content that has been mistakenly PUT as
     1537   a full representation.
     1538   Partial content updates are possible by targeting a separately identified
     1539   resource with state that overlaps a portion of the larger resource, or by
     1540   using a different method that has been specifically defined for partial
    15391541   updates (for example, the PATCH method defined in
    15401542   <xref target="RFC5789"/>).
    15411543</t>
    15421544<t>
    1543    Responses to the PUT method are not cacheable. If a PUT request passes
    1544    through a cache that has one or more stored responses for the effective
    1545    request URI, those stored responses will be invalidated (see
    1546    &p6-invalid;).
     1545   Responses to the PUT method are not cacheable. If a successful PUT request
     1546   passes through a cache that has one or more stored responses for the
     1547   effective request URI, those stored responses will be invalidated
     1548   (see &p6-invalid;).
    15471549</t>
    15481550</section>
Note: See TracChangeset for help on using the changeset viewer.