openstack/nova
Code Issues Proposed changes

Add a note about the 500->404 not requiring a microversion

Browse Source 
404 error code is always one of the return code when url or
resource does not exist, so 404 is an available status code for all the
Nova API. Then no microversion bump required for fixing 500 to 404
.

Change-Id: I4b1703e82cd89192b2ba4ce2603741e33dd26586
This commit is contained in:
ghanshyam 2015-10-02 20:41:04 +09:00
parent 03cae1c431
commit 39271bcd0c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/api_microversion_dev.rst
View File

@ -82,7 +82,7 @@ changed. The user contract covers many kinds of information such as:
Example: an API previously could return 200, 400, 403, 404 and the
change would make the API now also be allowed to return 409.
See [#f2]_ for the 400 and 403 cases.
See [#f2]_ for the 400, 403 and 404 cases.
- changing a status code on a particular response
@ -171,10 +171,11 @@ we need a microversion".
microversion is probably needed.
.. [#f2] The exception to not needing a microversion when returning a
previously unspecified error code is the 400 and 403 cases. This is
previously unspecified error code is the 400, 403 and 404 cases. This is
considered OK to return even if previously unspecified in the code since
it's implied given keystone authentication can fail with a 403 and API
validation can fail with a 400 for invalid json request body.
validation can fail with a 400 for invalid json request body. Request to
url/resource that does not exist always fails with 404.
In Code