Identity API v3 nonstandard response code format
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-api-site |
Fix Released
|
Wishlist
|
Jorge L. Williams |
Bug Description
This is similar to bugs 1338123 and 1338124 which I opened against the "Identity API v2.0 Reference", but this one is against the "Identity API v3" api-ref (http://
The error response codes are listed like this: "identityFault (400, 500, …), badRequest (400), unauthorized (401), forbidden (403), badMethod (405), overLimit (413), serviceUnavailable (503), itemNotFound (404)"
There are a few issues with this.
First, the way that response codes are described is nonstandard. The HTTP 1.1 standard lists the response codes and reason phrase, and HTTP servers respond with the code and phrase, like "400 Bad Request" and "503 Service Unavailable", not like "badRequest (400)" or "serviceUnavail
Second, this one has "identityFault (400, 500, …)". This is not useful because it seems to indicate that any response code is identityFault. "identityFault (400, 500, …)" should be removed from "Error response codes".
The text seems to indicate that 405 is "Bad Method", but HTTP 1.1 defines it as "405 Method Not Allowed" -- http://
Similar for 404. HTTP 1.1 defines the phrase for this as "Not Found" and not "Item Not Found" -- http://
Similar for 413. "overLimit (413)" should be "414 Request-URI Too Long" http://
affects: | openstack-manuals → openstack-api-site |
This is interesting... this page has response codes as I'd expect to see them: http:// docs.openstack. org/api/ openstack- network/ 2.0/content/ update_ extra_route. html