What are HTTP Status Codes?
HTTP (HyperText Transfer Protocol) Status code indicates the status of the client's request. It is part of the HTTP response and sends by the server. Status code is generated by the program or web server. Status code is part of the HTTP/1.1 standard (RFC 7231). Typically, the client will send a request and the server will respond to that client's request.
Now, the client(browser) will understand the response received from the server with the help of HTTP status codes. Based on the status code received in the response header or browser page the user will understand what is happening for the request made and the response received. Here, in this article, we have listed all the categories (1XX, 2XX, 3XX, 4XX, 5XX) of the HTTP status codes and mentioned some of the important status codes from each category.
HTTP Status Code Categories
|Sl.No||HTTP Status Code||Refers to|
What are (1XX, 2XX, 3XX, 4XX, 5XX) Status Codes?
1XX Codes are Informational Codes Indicating that the request initiated by the browser is continuing.
It means the action was successfully received, understood, and accepted.
It means further action must be taken in order to complete the request.
It means the request contains incorrect syntax or cannot be fulfilled.
It means the server failed to fulfill an apparently valid request.
#1) 1XX INFORMATIONAL RESPONSES
- 100 - Continue - The initial part of a request has been received and has not yet been rejected by the server.
- 101 - Switching Protocols - The server understands and is willing to comply with the client's request.
- 102 - Processing - An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.
- 103 - Early Hints - Used to return some response headers before final HTTP message.
#2) 2XX SUCCESSFUL RESPONSES
- 200 OK- The request has succeeded. The payload sent in a 200 response depends on the request method(GET, POST, etc).
- 201 - Created- The request has been fulfilled and has resulted in one or more new resources being created.
- 202 - Accepted- The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.
- 203 - Non-Authoritative Information - The request was successful but the enclosed payload has been modified from that of the origin server's 200 OK response by a transforming proxy.
- 204 - No Content- The server has successfully fulfilled the request and that there is no additional content to send in the response payload body.
- 205 - Reset Content.
- 206 - Parental Content.
#3) 3XX REDIRECTS
- 300 - Multiple Choices - The request has more than one possible response. The user-agent or user should choose one of them.
- 301 - Moved Permanently- The URL of the requested resource has been changed permanently. The new URL is given in the response.
- 303 - See Other - The server sent this response to direct the client to get the requested resource at another URI with a GET request.
- 302 - Found.
- 303 - See Other.
- 304 - Not Modified.
- 305 - Use Proxy.
- 307 - Temporary Redirect - The server sends this response to direct the client to get the requested resource at another URI with the same method that was used in the prior request.
- 308 - Permanent Redirect - The target resource has been assigned a new permanent URL and any future references to this resource ought to use one of the enclosed URLs.
#4) 4XX CLIENT ERROR
- 400 - Bad Request - The server could not understand the request due to invalid syntax.
- 401- Unauthorized- The request has not been applied because it lacks valid authentication credentials for the target resource.
- 403 - Forbidden - The server understood the request but refuses to authorize it.
- 404 - Not Found - The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- 405 - Method not allowed.
- 406 - Not acceptable.
- 407 - Proxy authentication required.
- 408 - Request Method -The server did not receive a complete request message within the time that it was prepared to wait.
- 409 - Conflict.
- 410 - Gone.
- 411 - Length required.
- 412 - Precondition failed.
- 413 - Request entity too large.
- 414 - URL too long.
- 415 - Unsupported media type.
#5) 5XX SERVER ERROR
- 500 - Internal Server Error - The server encountered an unexpected condition that prevented it from fulfilling the request.
- 501 - Not Implemented - The server does not support the functionality required to fulfill the request.
- 502 - Bad Gateway - The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- 503 - Service Unavailable - The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.
- 504 - Gateway Timeout - The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.
- 505 - HTTP version not supported.