HTTP Status Codes
src/tools/HTTP Status Codes
100

Continue

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

101

Switching Protocols

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

200

OK

Standard response for successful HTTP requests.

201

Created

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

204

No Content

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

301

Moved Permanently

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

302

Found

Was 'Moved Temporarily'. Tells the client to look at (browse to) another URL.

304

Not Modified

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

307

Temporary Redirect

The request should be repeated with another URI; however, future requests should still use the original URI.

400

Bad Request

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

401

Unauthorized

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

403

Forbidden

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

404

Not Found

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

405

Method Not Allowed

A request method is not supported for the requested resource.

408

Request Timeout

The server timed out waiting for the request.

418

I'm a teapot

The server refuses the attempt to brew coffee with a teapot.

429

Too Many Requests

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

500

Internal Server Error

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

502

Bad Gateway

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

503

Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance).

504

Gateway Timeout

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