About Lesson
HTTP status messages are part of the HTTP protocol used for communication between a client (such as a web browser) and a server. They indicate the status of a specific HTTP request. Here is a reference list of commonly encountered HTTP status messages along with their descriptions:
1xx Informational Responses:
- 100 Continue: The server acknowledges the initial part of the request and is ready to proceed with the client’s follow-up request.
2xx Success:
- 200 OK: The request was successful, and the server is returning the requested resource.
- 201 Created: The request was successful, and a new resource was created as a result.
- 204 No Content: The request was successful, but there is no content to return.
3xx Redirection:
- 301 Moved Permanently: The requested resource has been permanently moved to a new URL.
- 302 Found: The requested resource has been temporarily moved to a different URL.
- 304 Not Modified: The client’s cached version of the requested resource is still valid.
4xx Client Errors:
- 400 Bad Request: The server cannot understand the client’s request due to malformed syntax or invalid parameters.
- 401 Unauthorized: The client needs to provide valid authentication credentials for the requested resource.
- 403 Forbidden: The server understood the request, but the client is not allowed to access the requested resource.
- 404 Not Found: The requested resource could not be found on the server.
5xx Server Errors:
- 500 Internal Server Error: A generic server error occurred that prevents it from fulfilling the request.
- 502 Bad Gateway: The server acting as a gateway or proxy received an invalid response from an upstream server.
- 503 Service Unavailable: The server is currently unable to handle the request due to temporary overloading or maintenance.
These are just a few examples of HTTP status messages. The complete list includes more codes and specific messages. Each status message provides information about the outcome of an HTTP request, allowing clients and servers to communicate and handle different scenarios appropriately.
Join the conversation