HTTP Status Code Reference

Complete reference for all HTTP status codes. Click any code to see details.

1xx Informational

100Continue▼

Server received request headers; client should proceed.

101Switching Protocols▼

Server is switching to a different protocol.

102Processing▼

Server has received and is processing the request.

103Early Hints▼

Used to return response headers before final HTTP message.

2xx Success

200OK▼

Standard successful HTTP request.

201Created▼

Request succeeded and a new resource was created.

202Accepted▼

Request accepted but not yet completed.

203Non-Authoritative Information▼

Returned metadata is not from the origin server.

204No Content▼

Server processed request but no content to return.

205Reset Content▼

Server asks client to reset document view.

206Partial Content▼

Partial data returned (Range header request).

207Multi-Status▼

Multiple status codes (WebDAV).

208Already Reported▼

DAV binding members already enumerated.

226IM Used▼

Server fulfilled a GET request using delta encoding.

3xx Redirection

300Multiple Choices▼

Multiple options for the resource.

301Moved Permanently▼

Resource permanently moved to new URL.

302Found▼

Resource temporarily at a different URL.

303See Other▼

Response found at another URI using GET.

304Not Modified▼

Cached version is still valid.

307Temporary Redirect▼

Redirect temporarily, preserve method.

308Permanent Redirect▼

Redirect permanently, preserve method.

4xx Client Error

400Bad Request▼

Server cannot process due to client error.

401Unauthorized▼

Authentication required.

402Payment Required▼

Reserved for future use.

403Forbidden▼

Server refuses to fulfill the request.

404Not Found▼

Resource not found on the server.

405Method Not Allowed▼

HTTP method not supported for this resource.

406Not Acceptable▼

Server cannot produce acceptable response.

407Proxy Authentication Required▼

Must authenticate with proxy first.

408Request Timeout▼

Server timed out waiting for request.

409Conflict▼

Request conflicts with current server state.

410Gone▼

Resource permanently removed, no forwarding address.

411Length Required▼

Content-Length header required.

412Precondition Failed▼

Precondition in request headers evaluated to false.

413Content Too Large▼

Request entity exceeds server limits.

414URI Too Long▼

Request URI is longer than server can process.

415Unsupported Media Type▼

Media format not supported by server.

416Range Not Satisfiable▼

Range header field cannot be fulfilled.

417Expectation Failed▼

Server cannot meet Expect header requirements.

418I'm a teapot▼

Server refuses to brew coffee in a teapot.

422Unprocessable Content▼

Request was well-formed but semantically incorrect.

423Locked▼

Resource is locked (WebDAV).

424Failed Dependency▼

Request failed due to failed dependency (WebDAV).

425Too Early▼

Server unwilling to risk processing early data.

426Upgrade Required▼

Client should switch to a different protocol.

428Precondition Required▼

Request must be conditional.

429Too Many Requests▼

Rate limit exceeded.

431Request Header Fields Too Large▼

Request headers are too large.

451Unavailable For Legal Reasons▼

Resource unavailable due to legal reasons.

5xx Server Error

500Internal Server Error▼

Server encountered an unexpected condition.

501Not Implemented▼

Server doesn't support the request method.

502Bad Gateway▼

Server got invalid response from upstream.

503Service Unavailable▼

Server not ready to handle requests.

504Gateway Timeout▼

Gateway did not get a timely response.

505HTTP Version Not Supported▼

HTTP version not supported by server.

506Variant Also Negotiates▼

Circular reference in content negotiation.

507Insufficient Storage▼

Server unable to store the representation (WebDAV).

508Loop Detected▼

Infinite loop detected (WebDAV).

510Not Extended▼

Further extensions required for request.

511Network Authentication Required▼

Client needs to authenticate to gain network access.

About this tool

A comprehensive reference for HTTP status codes, request methods, headers, and MIME types. Look up any status code (200, 301, 404, 500, etc.) to get its meaning, when to use it, and common causes. Search headers to understand caching, authentication, CORS, and content negotiation. Bookmarkable for daily backend and API development.

How to Use the HTTP Reference

1Search for a status code (e.g. '404') or header name (e.g. 'Cache-Control').
2Read the description, typical use cases, and important notes.
3Browse by category: 2xx Success, 3xx Redirect, 4xx Client Error, 5xx Server Error.
4Click any header to see its syntax, valid values, and examples.
5Bookmark the tool for quick reference during API development.

Frequently Asked Questions

What is the difference between 301 and 302 redirects?+

301 is a permanent redirect - browsers and search engines cache it and transfer link equity to the new URL. 302 is temporary - browsers don't cache it and search engines keep indexing the original URL. Use 301 for permanent URL changes.

What does HTTP 429 Too Many Requests mean?+

The server is rate-limiting the client. The response should include a Retry-After header indicating when the client can try again. Implement exponential backoff in your API client when you encounter 429.

What is the difference between PUT and PATCH?+

PUT replaces the entire resource with the provided data. PATCH applies a partial update - only the fields included in the request are modified. Use PATCH when updating a subset of fields to avoid overwriting unrelated data.

What does the Content-Type header do?+

Content-Type tells the recipient the media type of the body. For API requests: application/json. For form submissions: application/x-www-form-urlencoded or multipart/form-data. The server uses this to parse the body correctly.

Looking for a deeper guide on this topic? Browse the Searchlight blog.

Visit the blog →

Related tools

View all Code Tools →