Merge "Add a note about the 400 response not requiring a microversion"
This commit is contained in:
@@ -65,7 +65,7 @@ changed. The user contract covers many kinds of information such as:
|
|||||||
Example: an API previously could return 200, 400, 403, 404 and the
|
Example: an API previously could return 200, 400, 403, 404 and the
|
||||||
change would make the API now also be allowed to return 409.
|
change would make the API now also be allowed to return 409.
|
||||||
|
|
||||||
See [#f2]_ for the 403 case.
|
See [#f2]_ for the 400 and 403 cases.
|
||||||
|
|
||||||
- changing a status code on a particular response
|
- changing a status code on a particular response
|
||||||
|
|
||||||
@@ -154,9 +154,10 @@ we need a microversion".
|
|||||||
microversion is probably needed.
|
microversion is probably needed.
|
||||||
|
|
||||||
.. [#f2] The exception to not needing a microversion when returning a
|
.. [#f2] The exception to not needing a microversion when returning a
|
||||||
previously unspecified error code is the 403 case. This is considered OK to
|
previously unspecified error code is the 400 and 403 cases. This is
|
||||||
return even if previously unspecified in the code since it's implied given
|
considered OK to return even if previously unspecified in the code since
|
||||||
keystone authentication can fail with a 403.
|
it's implied given keystone authentication can fail with a 403 and API
|
||||||
|
validation can fail with a 400 for invalid json request body.
|
||||||
|
|
||||||
|
|
||||||
In Code
|
In Code
|
||||||
|
Reference in New Issue
Block a user