Changeset 1168 for draft-ietf-httpbis/latest

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].

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (1 diff)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -1401 +1401 @@
          or will not be changed by the PUT. This is particularly important when the origin server uses internal configuration information
          related to the URI in order to set the values for representation metadata on GET responses. When a PUT representation is inconsistent
-         with the target resource, the origin server <em class="bcp14">SHOULD</em> either make them consistent, by transforming the representation or changing the resource configuration, or respond with a
-         409 (Conflict) status code and sufficient information to explain why the representation is unsuitable.
+         with the target resource, the origin server <em class="bcp14">SHOULD</em> either make them consistent, by transforming the representation or changing the resource configuration, or respond with an
+         appropriate error message containing sufficient information to explain why the representation is unsuitable. The 409 (Conflict)
+         or 415 (Unsupported Media Type) status codes are suggested, with the latter being specific to constraints on Content-Type
+         values.
       </p>
       <p id="rfc.section.7.6.p.5">For example, if the target resource is configured to always have a Content-Type of "text/html" and the representation being
          PUT has a Content-Type of "image/jpeg", then the origin server <em class="bcp14">SHOULD</em> do one of: (a) reconfigure the target resource to reflect the new media type; (b) transform the PUT representation to a format
-         consistent with that of the resource before saving it as the new resource state; or, (c) reject the request with a 409 response
+         consistent with that of the resource before saving it as the new resource state; or, (c) reject the request with a 415 response
          indicating that the target resource is limited to "text/html", perhaps including a link to a different resource that would
          be a suitable target for the new representation.

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1011 +1011 @@
    server &SHOULD; either make them consistent, by transforming the
    representation or changing the resource configuration, or respond
-   with a 409 (Conflict) status code and sufficient information
-   to explain why the representation is unsuitable.
+   with an appropriate error message containing sufficient information
+   to explain why the representation is unsuitable.  The 409 (Conflict)
+   or 415 (Unsupported Media Type) status codes are suggested, with the
+   latter being specific to constraints on Content-Type values.
 </t>
 <t>
@@ -1021 +1023 @@
    (b) transform the PUT representation to a format consistent with that
    of the resource before saving it as the new resource state; or,
-   (c) reject the request with a 409 response indicating that the target
+   (c) reject the request with a 415 response indicating that the target
    resource is limited to "text/html", perhaps including a link to a
    different resource that would be a suitable target for the new