406 - Not Acceptable
Quick Summary
Overview
What it means
The HTTP 406 Not Acceptable status code indicates that the target resource does not have a current representation that would be acceptable to the user agent. In the context of web communication, this is a standard response from the server indicating the specific state of your request.
Why it occurs
This typically occurs when a client makes a request that contains invalid data, lacks credentials, or requests a non-existent resource. The server responds with 406 to inform the client of the outcome.
Where you'll see it
You will commonly encounter the 406 error in browser network tabs, API response payloads, server error logs (like Apache or Nginx), and uptime monitoring tools. It affects both direct user navigation and background AJAX/fetch requests.
Real-world impact
If left unresolved, a 406 error can lead to degraded user experience, blocked workflows, and potential negative impacts on SEO if search engine crawlers consistently encounter it on public-facing pages.
Common Symptoms
When a 406 error occurs, users and systems typically experience the following behaviors:
- The web browser displays a generic or custom "406 Not Acceptable" error page.
- API requests return a response payload containing a 406 status code.
- Frontend applications may show a "failed to load data" or "network error" toast notification.
- Server access logs record requests terminating with the 406 status.
- Monitoring systems and webhooks trigger alerts for elevated 406 error rates.
Main Causes
Understanding why a 406 happens is the first step to resolving it. Here are the most common deep technical causes:
The server processing the request may have incorrect routing rules, strict security policies, or syntax errors in its configuration files that force it to return a 406 status.
The application sending the request might be appending invalid headers, using an unsupported HTTP method, or lacking necessary authentication tokens.
If your architecture involves microservices or reverse proxies, the upstream server might be timing out, crashing, or returning unexpected data.
Issues related to DNS resolution, CDN caching layers, or strict corporate firewalls can intercept and reject requests before they reach the actual application logic.
!Step-by-Step Solutions
Follow these step-by-step instructions to resolve the 406 error. Start with the first step and proceed sequentially.
Verify Request Parameters and Headers
Before diving into server configs, ensure that the outgoing request is perfectly formatted. Check the URL path, query parameters, HTTP method, and necessary headers (like Content-Type and Authorization).
Why this works
Eliminating client-side formatting issues is the fastest way to resolve request-based errors, as servers are strict about HTTP specification compliance.
Expected result
If the request was malformed, correcting it will result in a successful 2xx response.
fetch('https://api.example.com/data', {
method: 'GET',
headers: {
'Accept': 'application/json',
'Authorization': 'Bearer YOUR_TOKEN'
}
})
.then(res => {
if(!res.ok) throw new Error(`HTTP error! status: ${res.status}`);
return res.json();
});Inspect Server and Error Logs
Access your server's diagnostic logs to find the exact stack trace or error message associated with the request that generated the 406 status.
Why this works
Logs provide the exact context—such as a missing file, a database connection timeout, or a syntax error—that generic HTTP status codes obscure.
Expected result
You will find a specific error message guiding you to the exact line of code or configuration directive causing the issue.
tail -f /var/log/nginx/error.logtail -f /var/log/apache2/error.logReview Application Routing Logic
Ensure that your application framework (e.g., Express, Django, Laravel) is correctly matching the incoming route and has the required controller logic implemented.
Why this works
Frameworks will automatically return specific errors (like 404 or 405) if they cannot find a matching route definition or controller method for the request.
Expected result
Adding or fixing the route definition will allow the framework to process the request normally.
app.get('/api/resource', (req, res) => {
// Implementation here
res.status(200).json({ success: true });
});Clear Caches and Flush DNS
If you have recently made changes to your server or DNS records, your local machine, browser, or a middleman CDN might be serving a stale error page. Clear all intermediary caches.
Why this works
Clearing caches forces a fresh request to be sent all the way to the origin server, bypassing any outdated state.
Expected result
The fresh request will reach the updated server logic, potentially resolving the error.
ipconfig /flushdnssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderAdvanced Developer Fixes
If you have server access, you can implement these backend configurations or middleware patterns to handle or prevent 406 errors.
Nginx Reverse Proxy Configuration
nginxEnsure that the upstream service (localhost:3000) is running and accessible. Intercepting errors allows Nginx to serve custom error pages.
Warning: Always test your configuration using 'nginx -t' before reloading the service.
server {
listen 80;
server_name example.com;
location / {
proxy_pass http://localhost:3000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
# Handle specific errors
proxy_intercept_errors on;
error_page 406 /custom_406.html;
}
}Apache .htaccess Error Handling
apachePlace this in your site's root .htaccess file to gracefully handle 406 scenarios with a branded page.
Warning: Mod_rewrite must be enabled on your Apache server for rewrite rules to function.
RewriteEngine On
# Custom Error Document definition
ErrorDocument 406 /errors/406.html
# Ensure correct permissions are granted
<Directory /var/www/html>
AllowOverride All
Require all granted
</Directory>Node.js Global Error Middleware
javascriptThis middleware catches exceptions thrown in earlier routes and normalizes the API response structure.
Warning: Do not expose stack traces to the client in a production environment.
app.use((err, req, res, next) => {
console.error(err.stack);
const status = err.status || 400;
res.status(status).json({
error: {
message: err.message || 'An unexpected error occurred',
status: status
}
});
});Platform-Specific Fixes
Resolving 406 on Windows
- 1
Open Command Prompt as Administrator and run 'ipconfig /flushdns' to clear stale DNS records.
- 2
Check Windows Defender Firewall rules that might be blocking outbound port access.
- 3
Clear browser cache by pressing Ctrl + Shift + Del.
Common Variations & Aliases
Prevention Strategies
- Implement comprehensive automated testing (unit, integration, and e2e) in your CI/CD pipeline.
- Utilize robust monitoring and alerting tools like Datadog, New Relic, or Sentry to catch anomalies early.
- Keep all server software, frameworks, and third-party dependencies updated to their latest stable versions.
- Enforce strict validation on all incoming client payloads to prevent malformed data from crashing backend services.
- Configure appropriate timeouts and retry logic with exponential backoff for all external network requests.
Real-World Scenarios
1406 Error After Deployment
A new version of the application was deployed, but environment variables were missing or a database migration failed to run, causing the server to respond with a 406 status to all incoming requests.
2406 Only on Specific Devices
Users on mobile networks experience the 406 error while desktop users on broadband do not, indicating a potential issue with request timeouts, MTU sizes, or aggressive mobile carrier caching proxies.
3Intermittent 406 Spikes During High Traffic
The error only appears during peak usage hours when the server runs out of available memory or database connection pool limits are exhausted, resulting in a cascade of 406 failures.
Frequently Asked Questions
The fastest way to troubleshoot a 406 error is to first determine if it's a client or server issue. If it's a 4xx error, double-check your request URL, headers, and payload. If it's a 5xx error, check your server error logs immediately to find the root cause.
Typically, standard HTTP status codes like 406 are not inherently dangerous; they are expected protocol behaviors. However, they might indicate an underlying vulnerability or misconfiguration if they are unexpected or expose stack traces to the public.
Yes. Aggressive local antivirus software or corporate firewalls can intercept HTTP traffic, modify headers, or block requests entirely, leading the browser or application to surface a 406 or similar network error.
If the 406 response was erroneously cached by your browser or a CDN, clearing the cache forces a fresh request to the server, which may resolve the issue if the origin server has already been fixed.
Consistent client or server errors on public-facing URLs will negatively impact SEO. Search engine crawlers will flag the pages as inaccessible or broken, which can lead to de-indexing or lowered rankings over time.
Developer Notes
HTTP/1.1 406 Not Acceptable
Content-Type: application/json
Connection: close
Date: Fri, 08 May 2026 05:48:11 GMT{
"error": {
"code": 406,
"message": "Not Acceptable",
"details": "The request could not be completed successfully."
}
}Official Specifications
- RFC 9110: HTTP Semantics
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Advanced Use Cases
Explore advanced scenarios, distributed system implementations, and infrastructure considerations for 406 errors.
Content Negotiation for Multi-Format Enterprise APIs
Scenario
A large enterprise API platform supports multiple response formats such as JSON, XML, CSV, Protocol Buffers, or localized content variants depending on client capabilities and integration requirements.
How it Works
The client sends headers like 'Accept', 'Accept-Language', or 'Accept-Encoding' specifying the formats it can process. If the server cannot generate any compatible representation, it responds with 'HTTP/1.1 406 Not Acceptable' and may include metadata describing supported formats.
Unsupported Content Negotiation
GET /reports HTTP/1.1
Accept: application/protobuf
HTTP/1.1 406 Not Acceptable
Content-Type: application/json
{
"error": "unsupported_format",
"supportedFormats": [
"application/json",
"application/xml"
]
}Benefits
- Enforces strict API format compatibility
- Supports multi-format enterprise integrations
- Improves client-server interoperability
- Enables localization-aware responses
- Helps prevent incompatible payload handling
Best Practices
- Return supported format metadata clearly
- Validate Accept headers strictly
- Document negotiable formats thoroughly
- Avoid silently changing response formats
- Support graceful fallback strategies
Developer Notes
- •Works well with Accept and Accept-Language headers
- •Useful for API version negotiation
- •Can support localization-aware systems
- •Helpful for machine-to-machine integrations
Real World Example
Banking APIs, enterprise ERP systems, healthcare integrations, and government data services often use strict content negotiation with 406 responses.
Why It's Underrated
Many developers always force JSON responses and overlook how important protocol-level negotiation becomes in enterprise interoperability environments.
Security Impact
Strict content negotiation reduces ambiguity and prevents clients from accidentally processing unsupported or unsafe payload formats.
Performance Impact
Negotiating optimized formats such as compressed binary payloads can significantly improve bandwidth efficiency.
Advanced Architecture: Multi-Representation API Platforms
Large-scale enterprise APIs often dynamically generate multiple representations of the same resource for mobile clients, legacy systems, analytics pipelines, and machine integrations.