37185428dd
In addition to DELETE requests, keystone may return an HTTP 204 as a success code for PUT[1] and HEAD[2] requests. It would be quite disconcerting if keystone were actually deleting resources during such additive and read-only operations, so this patch simplifies the 204 description so that it is truthful in all of its use cases. [1] https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=assign-role-to-group-on-domain-detail#assign-role-to-group-on-domain [2] https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=check-whether-user-belongs-to-group-detail#check-whether-user-belongs-to-group Change-Id: I0e4f9df873a831d7329e71b77818bc47d3c2bbb2
65 lines
1.7 KiB
YAML
65 lines
1.7 KiB
YAML
# Success Codes
|
|
|
|
200:
|
|
default: |
|
|
Request was successful.
|
|
201:
|
|
default: |
|
|
Resource was created and is ready to use.
|
|
202:
|
|
default: |
|
|
Request was accepted for processing, but the processing has not been
|
|
completed. A 'location' header is included in the response which contains
|
|
a link to check the progress of the request.
|
|
204:
|
|
default: |
|
|
The server has fulfilled the request.
|
|
300:
|
|
default: |
|
|
There are multiple choices for resources. The request has to be more
|
|
specific to successfully retrieve one of these resources.
|
|
|
|
# Error Codes
|
|
|
|
400:
|
|
default: |
|
|
Some content in the request was invalid.
|
|
401:
|
|
default: |
|
|
User must authenticate before making a request.
|
|
403:
|
|
default: |
|
|
Policy does not allow current user to do this operation.
|
|
404:
|
|
default: |
|
|
The requested resource could not be found.
|
|
405:
|
|
default: |
|
|
Method is not valid for this endpoint.
|
|
406:
|
|
default: |
|
|
The requested API version is not supported by the API.
|
|
409:
|
|
default: |
|
|
This operation conflicted with another operation on this resource.
|
|
413:
|
|
default: |
|
|
The request is larger than the server is willing or able to process.
|
|
415:
|
|
default: |
|
|
The request entity has a media type which the server or resource does
|
|
not support.
|
|
500:
|
|
default: |
|
|
Something went wrong inside the service. This should not happen usually.
|
|
If it does happen, it means the server has experienced some serious
|
|
problems.
|
|
501:
|
|
default: |
|
|
The server either does not recognize the request method, or it lacks the
|
|
ability to fulfill the request.
|
|
503:
|
|
default: |
|
|
Service is not available. This is mostly caused by service configuration
|
|
errors which prevents the service from successful start up.
|