412
HTTP 412 Precondition Failed
4xx Client Error
- Home
- > HTTP Status Codes >
- > 4xx >
- 412
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
4xx Client Error
RFC 7232, Section 4.2
What is HTTP 412 Precondition Failed?
The 412 (Precondition Failed) status code indicates that one or more conditions given in the request header fields evaluated to false when tested on the server. This is used with conditional requests using headers like If-Match, If-None-Match, If-Modified-Since, or If-Unmodified-Since.
Common Use Cases
- Optimistic concurrency control with If-Match
- Conditional updates to prevent overwriting changes
- Cache validation with ETag conditions