lboka/document-database-service
1
0
Fork 0
forked from docs/document-database-service
Code Pull Requests Activity
document-database-service/api-ref/source/appendix/status_code.rst
proposalbot d748eab4d5 Changes to dds_api-ref from docs/doc-exports#410 (DDS API 20221101 version 
DDS

Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com>
Co-authored-by: proposalbot <proposalbot@otc-service.com>
Co-committed-by: proposalbot <proposalbot@otc-service.com>
2022-11-09 23:26:45 +00:00

12 KiB
Raw Blame History

original_name

dds_status_code.html

Status Code

  • Normal

    Status Code Message Description
    200 OK Request succeeded.
    202 Accepted Asynchronous request submitted successfully.

  • Abnormal

    Status Code Message Description
    400 Bad Request

    Invalid request.

    The client should not repeat the request without modifications.
    401 Unauthorized The authorization information provided by the client is incorrect or invalid. Check the username and password.
    403 Forbidden

    The request is rejected.

    The server has received and understood the request; yet it refused to respond, because the request is set to deny access. Do not retry the request before modification.
    404 Not Found

    The requested resource cannot be found.

    The client should not repeat the request without modifications.
    405 Method Not Allowed

    The method specified in the request is not supported for the requested resource.

    The client should not repeat the request without modifications.
    409 Conflict

    The request could not be processed due to a conflict.

    This status code indicates that the resource that the client attempts to create already exits, or the request fails to be processed because of the update of the conflict request.
    413 Request Entity Too Large The request is larger than that a server is able to process. The server may close the connection to prevent the client from continuing the request. If the server temporarily cannot process the request, the response will contain a Retry-After header field.
    415 Unsupported Media Type The server is unable to process the media format in the request.
    422 Unprocessable Entity The request is well-formed but is unable to be processed due to semantic errors.
    500 Internal Server Error The server is able to receive the request but it could not understand the request.
    501 Not Implemented The server does not support the requested function.
    503 Service Unavailable

    The requested service is invalid.

    The client should not repeat the request without modifications.