4xx Client Error
29 status codes
- Home
- > HTTP Status Codes >
- 4xx
Menu
Blog
Encoder & Decoder
Utility
General
- SMS Counter
- Check String Length
- Password Generator
- CHMOD Calculator
- Cron Job Command Generator
- Shortened URL Checker
- RGB to HEX Converter
- Epoch Unix Timestamp Converter
- UUID & ULID Generator
- Timezone Converter
Image Tools
PDF Tools
Minifier
Web Dev
- QR Code Generator
- Barcode Generator
- Lorem Ipsum Generator
- HTML Entities
- MIME Types Table Reference
- HTTP Status Codes
- What Is My IP Address
- JSON Formatter & Validator
- SQL Formatter & Beautifier
- XML Formatter & Beautifier
- YAML Formatter & Beautifier
- Text Case Converter
- JSON to CSV Converter
- Clipboard Workspace
- JSON Validator & Repair
- JSON Schema Validator
Laravel
- All Laravel Tools
- Collection Playground
- Eloquent Relationship Generator
- Validation Rule Generator
- Migration Generator
- Scheduler Generator
- Middleware Pipeline Visualizer
- Eloquent Query Builder Generator
- Laravel Artisan Cheat Sheet
Tailwind
These codes indicate that the request contains bad syntax or cannot be fulfilled by the server. The error is typically on the client side — malformed syntax, unauthorized access, or requesting a resource that doesn't exist.
| Code | Title | Description | RFC |
|---|---|---|---|
| 400 | Bad Request | The server cannot or will not process the request due to something perceived as a client error. | RFC 7231, Section 6.5.1 |
| 401 | Unauthorized | The request has not been applied because it lacks valid authentication credentials for the target resource. | RFC 7235, Section 3.1 |
| 402 | Payment Required | This status code is reserved for future use and is intended for digital payment systems. | RFC 7231, Section 6.5.2 |
| 403 | Forbidden | The server understood the request but refuses to authorize it. | RFC 7231, Section 6.5.3 |
| 404 | Not Found | The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. | RFC 7231, Section 6.5.4 |
| 405 | Method Not Allowed | The method received in the request-line is known by the origin server but not supported by the target resource. | RFC 7231, Section 6.5.5 |
| 406 | Not Acceptable | The target resource does not have a current representation that would be acceptable to the user agent. | RFC 7231, Section 6.5.6 |
| 407 | Proxy Authentication Required | The client must first authenticate itself with the proxy. | RFC 7235, Section 3.2 |
| 408 | Request Timeout | The server did not receive a complete request message within the time it was prepared to wait. | RFC 7231, Section 6.5.7 |
| 409 | Conflict | The request could not be completed due to a conflict with the current state of the target resource. | RFC 7231, Section 6.5.8 |
| 410 | Gone | The target resource is no longer available at the origin server and this condition is likely permanent. | RFC 7231, Section 6.5.9 |
| 411 | Length Required | The server refuses to accept the request without a defined Content-Length header. | RFC 7231, Section 6.5.10 |
| 412 | Precondition Failed | One or more conditions given in the request header fields evaluated to false. | RFC 7232, Section 4.2 |
| 413 | Content Too Large | The request body is larger than the server is willing or able to process. | RFC 7231, Section 6.5.11 |
| 414 | URI Too Long | The target URI is longer than the server is willing to interpret. | RFC 7231, Section 6.5.12 |
| 415 | Unsupported Media Type | The origin server is refusing to service the request because the payload is in a format not supported. | RFC 7231, Section 6.5.13 |
| 416 | Range Not Satisfiable | None of the ranges in the request's Range header field overlap the current extent of the selected resource. | RFC 7233, Section 4.4 |
| 417 | Expectation Failed | The expectation given in the request's Expect header field could not be met. | RFC 7231, Section 6.5.14 |
| 418 | I'm a Teapot | This code was defined in 1998 as an April Fools' joke in RFC 2324, Hyper Text Coffee Pot Control Protocol. | RFC 2324, Section 2.3.2 |
| 421 | Misdirected Request | The request was directed at a server that is not able to produce a response. | RFC 7540, Section 9.1.2 |
| 422 | Unprocessable Content | The server understands the content type and syntax of the request body but was unable to process the contained instructions. | RFC 9110, Section 15.5.21 |
| 423 | Locked | The source or destination resource of a method is locked (WebDAV). | RFC 4918, Section 11.3 |
| 424 | Failed Dependency | The method could not be performed on the resource because the requested action depended on another action that failed (WebDAV). | RFC 4918, Section 11.4 |
| 425 | Too Early | The server is unwilling to risk processing a request that might be replayed. | RFC 8470, Section 5.2 |
| 426 | Upgrade Required | The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades. | RFC 7231, Section 6.5.15 |
| 428 | Precondition Required | The origin server requires the request to be conditional to prevent the lost update problem. | RFC 6585, Section 3 |
| 429 | Too Many Requests | The user has sent too many requests in a given amount of time (rate limiting). | RFC 6585, Section 4 |
| 431 | Request Header Fields Too Large | The server is unwilling to process the request because its header fields are too large. | RFC 6585, Section 5 |
| 451 | Unavailable For Legal Reasons | The server is denying access to the resource as a consequence of a legal demand. | RFC 7725, Section 3 |