Dtools
WEB-07

HTTP Status Code Lookup

Look up what an HTTP status code means.

100 Continue

The initial part of the request has been received and the client should continue.

101 Switching Protocols

The server is switching protocols as requested by the client.

200 OK

The request succeeded.

201 Created

The request succeeded and a new resource was created.

202 Accepted

The request was accepted for processing, but isn't complete yet.

204 No Content

The request succeeded but there's no content to return.

206 Partial Content

Only part of the resource is being delivered, per a Range header.

301 Moved Permanently

The resource has permanently moved to a new URL.

302 Found

The resource temporarily resides at a different URL.

304 Not Modified

The cached version is still valid; no need to re-download.

307 Temporary Redirect

Like 302, but the request method must not change.

308 Permanent Redirect

Like 301, but the request method must not change.

400 Bad Request

The server can't process the request due to a client error.

401 Unauthorized

Authentication is required and has failed or not been provided.

403 Forbidden

The client doesn't have permission to access this resource.

404 Not Found

The server can't find the requested resource.

405 Method Not Allowed

The request method isn't supported for this resource.

408 Request Timeout

The server timed out waiting for the request.

409 Conflict

The request conflicts with the current state of the resource.

410 Gone

The resource is permanently gone and won't come back.

415 Unsupported Media Type

The request payload format isn't supported.

422 Unprocessable Entity

The request is well-formed but has semantic errors.

429 Too Many Requests

The client has sent too many requests in a given time.

500 Internal Server Error

A generic error occurred on the server.

501 Not Implemented

The server doesn't support the functionality required.

502 Bad Gateway

The server got an invalid response from an upstream server.

503 Service Unavailable

The server isn't ready to handle the request right now.

504 Gateway Timeout

The upstream server didn't respond in time.

More in Web Tools