406
406 Not Acceptable Error
What This Error Means
The 406 Not Acceptable error occurs when a server is able to locate the requested resource but cannot deliver it in any format that matches the criteria specified by the client. Modern browsers and API clients send Accept headers that describe which response formats, languages, or character encodings they are willing to process. This mechanism is known as content negotiation. When the server evaluates these headers and determines that none of its available representations satisfy the request, it stops processing and returns a 406 response. In practice, this error is often misleading. While it is defined as a client-side issue, it frequently appears due to restrictive server security rules or misconfigured content handling rather than an actual incompatibility in formats.
Common Causes
- Security modules on the server rejecting requests based on header inspection, even when the request itself is valid.
- The client explicitly requesting a response format that the server does not support.
- Language negotiation failing because the client prefers a language that is not available on the server.
- Character encoding requirements sent by the client that the server is unable to satisfy.
- Application-level filtering that blocks requests with uncommon or unexpected Accept headers.
How to Fix It (For Users)
- 1 Disable VPNs or proxies that may be modifying request headers before they reach the server.
- 2 Clear browser data to ensure outdated or corrupted headers are not being reused.
- 3 Try accessing the resource from a different browser or device to rule out local configuration issues.
For Site Owners / Developers
- Review server security logs to identify rules that are rejecting requests with a 406 response.
- Ensure the server is configured to serve all response formats required by the application.
- Inspect incoming request headers to understand what the client is asking for and why negotiation fails.
- Temporarily disable security or filtering layers to confirm whether they are the source of the rejection.
- Implement a fallback response format so the server can return a valid response when negotiation fails.
When It Is NOT Your Fault
If a server-side security update or configuration change introduces overly strict filtering, valid client requests may be rejected even though they are correctly formed.
Check if this outage affects everyone globally
This error often indicates a wider problem. Use our tool to verify if the site is down for everyone.
Check Website Status →Recommended Tool to Prevent This Error
Prevent server timeouts and resource exhaustion with scalable cloud infrastructure.