Ignore:
Timestamp:
Mar 11, 2011, 8:04:37 PM (9 years ago)
Author:
fielding@…
Message:

Based on list discussion, suggest both 409 and 415 as status
codes when a PUT representation conflicts with the nature of
the identified resource, and use 415 in the example that is
specific to media types. This is a correction to [1158].

File:
1 edited

Legend:

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

    r1167 r1168  
    10111011   server &SHOULD; either make them consistent, by transforming the
    10121012   representation or changing the resource configuration, or respond
    1013    with a 409 (Conflict) status code and sufficient information
    1014    to explain why the representation is unsuitable.
     1013   with an appropriate error message containing sufficient information
     1014   to explain why the representation is unsuitable.  The 409 (Conflict)
     1015   or 415 (Unsupported Media Type) status codes are suggested, with the
     1016   latter being specific to constraints on Content-Type values.
    10151017</t>
    10161018<t>
     
    10211023   (b) transform the PUT representation to a format consistent with that
    10221024   of the resource before saving it as the new resource state; or,
    1023    (c) reject the request with a 409 response indicating that the target
     1025   (c) reject the request with a 415 response indicating that the target
    10241026   resource is limited to "text/html", perhaps including a link to a
    10251027   different resource that would be a suitable target for the new
Note: See TracChangeset for help on using the changeset viewer.