4xx Client Error
4xx
codes are error responses that indicate an issue on the client's end, potentially due to a network problem.
4xx
codes can be used as a response to any request method.- The origin server should include an explanation, which should be displayed by the User-Agent, except in the case of a
HEAD
request. - Custom rules can return any response code in the range of
400–499
on your HTML page if the site owner has created a rule with the Block action and configured a custom response code. For more details, refer to custom response.
For a complete description of this error refer to the Error 400 page.
For a complete description of this error refer to the Error 401 page.
The 402 Payment Required
status code is reserved for future use and is not yet implemented according to the standards outlined in RFC 7231 ↗.
For a complete description of this error refer to the Error 403 page.
For a complete description of this error refer to the Error 404 page.
For a complete description of this error refer to the Error 405 page.
For a complete description of this error refer to the Error 406 page.
For a complete description of this error refer to the Error 407 page.
For a complete description of this error refer to the Error 408 page.
For a complete description of this error refer to the Error 409 page.
For a complete description of this error refer to the Error 410 page.
For a complete description of this error refer to the Error 411 page.
For a complete description of this error refer to the Error 412 page.
For a complete description of this error refer to the Error 413 page.
For a complete description of this error refer to the Error 414 page.
For a complete description of this error refer to the Error 415 page.
For a complete description of this error refer to the Error 416 page.
For a complete description of this error refer to the Error 417 page.
For a complete description of this error refer to the Error 429 page.
For a complete description of this error refer to the Error 451 page.
For a complete description of this error refer to the Error 499 page.
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Products
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- 2025 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark