DevToolBox
Pipeline
DevToolBox
Pipeline
← All Tools

HTTP Status Reference

Reference for HTTP status codes and their meanings.

100Continue

The server has received the request headers and the client should proceed to send the request body.

101Switching Protocols

The requester has asked the server to switch protocols and the server has agreed.

102Processing

The server has received and is processing the request, but no response is available yet.

200OK

The request has succeeded.

201Created

The request has been fulfilled and has resulted in a new resource being created.

202Accepted

The request has been accepted for processing, but the processing has not been completed.

204No Content

The server successfully processed the request and is not returning any content.

206Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

301Moved Permanently

The resource has been permanently moved to a new URL.

302Found

The resource resides temporarily under a different URL.

304Not Modified

The resource has not been modified since the version specified by the request headers.

307Temporary Redirect

The request should be repeated with another URL, but future requests should use the original URL.

308Permanent Redirect

The request and all future requests should be repeated using another URL.

400Bad Request

The server cannot process the request due to a client error.

401Unauthorized

Authentication is required and has failed or has not been provided.

403Forbidden

The client does not have access rights to the content.

404Not Found

The server cannot find the requested resource.

405Method Not Allowed

The request method is not supported for the requested resource.

408Request Timeout

The server timed out waiting for the request.

409Conflict

The request could not be processed because of conflict in the current state of the resource.

413Payload Too Large

The request is larger than the server is willing or able to process.

415Unsupported Media Type

The media format of the requested data is not supported by the server.

422Unprocessable Entity

The request was well-formed but was unable to be followed due to semantic errors.

429Too Many Requests

The user has sent too many requests in a given amount of time.

500Internal Server Error

The server has encountered a situation it does not know how to handle.

501Not Implemented

The request method is not supported by the server and cannot be handled.

502Bad Gateway

The server received an invalid response from the upstream server.

503Service Unavailable

The server is not ready to handle the request.

504Gateway Timeout

The server is acting as a gateway and cannot get a response in time.