Search, filter, and inspect definitions and descriptions of standard and proprietary HTTP client-server response headers.
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
Standard response for successful HTTP requests. The actual response will depend on the request method used.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request, but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
This and all future requests should be directed to the given URI.
Tells the client to look at another (temporary) URL. The original method should still be used.
Indicates that the resource has not been modified since the version specified by the request headers.
In this case, the request should be repeated with another URI; however, future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot or will not process the request due to an apparent client error.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
The request was a valid request, but the server is refusing to respond to it. The user might not have the necessary permissions.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
Indicates that the request could not be processed because of conflict in the current state of the resource.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server cannot handle the request (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Web architectures rely on status headers to communicate request outcomes securely. From standard success states like 200 OK and 201 Created, redirections like 301 and 304, to client limits (429 Rate Limited, 403 Forbidden) and server crashes (502 Bad Gateway), understanding response layers helps developers build high-reliability APIs.