Scribd
Upload
52 views

Error Codes in DevOps

The document provides explanations for common HTTP status codes, organized into categories for informational responses, successful responses, redirection responses, client error responses, and server error responses. Status codes include 100, 101, 200, 301, 404, 500 and descriptions of their meanings.

Uploaded by

Vinod Solanke
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
52 views

Error Codes in DevOps

The document provides explanations for common HTTP status codes, organized into categories for informational responses, successful responses, redirection responses, client error responses, and server error responses. Status codes include 100, 101, 200, 301, 404, 500 and descriptions of their meanings.

Uploaded by

Vinod Solanke
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

DevOps Shack

Error Codes IN DevOps .

Status Code Category Explanation


1xx: Requests received,
Informational continuing process.
The initial part of a request has been received and has
100 Continue
not yet been rejected by the server.
The requester has asked the server to switch protocols
101 Switching Protocols
and the server has agreed to do so.
The action was successfully
2xx: Success received, understood, and
accepted.
The request has succeeded. The meaning of the success
200 OK depends on the HTTP method: GET, HEAD, POST,
TRACE.
The request has been fulfilled and resulted in a new
201 Created
resource being created.
The request has been accepted for processing, but the
202 Accepted
processing has not been completed.
The server successfully processed the request and is not
204 No Content
returning any content.
Further action must be
3xx:
taken in order to complete
Redirection
the request.
The URL of the requested resource has been changed
301 Moved Permanently
permanently. The new URL is given in the response.
The server found a temporary redirection. This response
302 Found
is only used for HTTP 1.0 compatibility.
The response to the request can be found under
303 See Other
another URI using the GET method.
Indicates that the resource has not been modified since
304 Not Modified
the last request.
4xx: Client The request contains bad
Error syntax or cannot be fulfilled.
The server cannot or will not process the request due to
400 Bad Request an apparent client error (e.g., malformed request
syntax).
Similar to 403 Forbidden, but specifically for use when
401 Unauthorized authentication is required and has failed or has not yet
been provided.
The request was a valid request, but the server is
403 Forbidden
refusing to respond to it.
The requested resource could not be found but may be
404 Not Found
available again in the future.
Indicates that the request could not be processed
409 Conflict because of conflict in the request, such as an edit
conflict in the case of multiple updates.
5xx: Server The server failed to fulfill an
Error apparently valid request.
The server encountered an unexpected condition which
500 Internal Server Error
prevented it from fulfilling the request.
The server was acting as a gateway or proxy and
502 Bad Gateway
received an invalid response from the upstream server.
The server is currently unavailable (overloaded or down
503 Service Unavailable
for maintenance).
The server was acting as a gateway or proxy and did
504 Gateway Timeout
not receive a timely response from the upstream server.

You might also like