You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2015/03/13 22:44:39 UTC
[jira] [Created] (QPID-6449) [Java Broker] Change REST interfaces
to return 422 status code when validation fails for create/update request
Alex Rudyy created QPID-6449:
--------------------------------
Summary: [Java Broker] Change REST interfaces to return 422 status code when validation fails for create/update request
Key: QPID-6449
URL: https://issues.apache.org/jira/browse/QPID-6449
Project: Qpid
Issue Type: Improvement
Components: Java Broker
Affects Versions: 0.30, 0.32
Reporter: Alex Rudyy
Assignee: Alex Rudyy
At the moment 409 status code is returned for almost every client error.
In order to distinguish validation failures from real conflicts 422 status code can be returned for the former.
422 status code will be returned when invalid attributes values or not all required attributes are provided in REST requests to create or update configured object
{quote}
The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org