HTTP Response Status Codes – Common Subset

Posted 2024-07-24.

The status codes are defined by RFC 9110 (httpwg.org).
Code	Class	Description
Code	Class	Description
301 Moved Permanent	Redirection	The URL of the requested resource has been changed permanently. The new URL is given in the response.
302 Found	Redirection	This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
304 Not Modified	Redirection	This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
403 Forbidden	Client Error	The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
404 Not Found	Client Error	The server cannot find the requested resource. In the browser, this means the URL is not recognized. In anAPI, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.
405 Method Not Allowed	Client Error	The request method is known by the server but is not supported by the target resource. For example, an API may not allow calling DELETE to remove a resource.
410 Gone	Client Error	This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for "limited-time, promotional services". APIs should not feel compelled to indicate resources that have been deleted with this status code.