Back to Tools

HTTP Status Codes

Quick reference guide for HTTP status codes.

1xx Informational

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 to do so.

2xx Success

200OK

Standard response for successful HTTP requests.

201Created

The request has been fulfilled, resulting in the creation of a new resource.

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.

3xx Redirection

301Moved Permanently

This and all future requests should be directed to the given URI.

302Found

Tells the client to look at (browse to) another URL.

304Not Modified

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

4xx Client Error

400Bad Request

The server cannot or will not process the request due to an apparent client error.

401Unauthorized

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

403Forbidden

The request contained valid data and was understood by the server, but the server is refusing action.

404Not Found

The requested resource could not be found but may be available in the future.

405Method Not Allowed

A request method is not supported for the requested resource.

429Too Many Requests

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

5xx Server Error

500Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

502Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503Service Unavailable

The server cannot handle the request (because it is overloaded or down for maintenance).

504Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.