SiteError.comYour friendly guide to HTTP status codes
Status CodesBlog
  1. Home
  2. AWS ELB
  3. 463 Too Many IPs in X-Forwarded-For

463 Too Many IPs in X-Forwarded-For

๐Ÿ”—
463
Too Many IPs in X-Forwarded-For

Example HTTP Response

HTTP Response
HTTP/1.1 463 X-Forwarded-For Header with More Than 30 IP Addresses
Content-Type: text/html
Connection: close

<html><body>Too many IP addresses in X-Forwarded-For header</body></html>
Common Causes
  • Request passed through more than 30 proxy servers
  • Malicious attempt to overflow the X-Forwarded-For header
  • Misconfigured proxy chain
  • Proxy loop causing IP addresses to accumulate
  • Attack vector attempting header manipulation
  • Multiple CDN/proxy layers without proper header management
  • Nested load balancers without header cleanup
Technical Details

What does this mean?

Your forwarding chain is way too long! It's like a game of telephone that went through 30+ people - we're cutting you off before this gets ridiculous. How many proxies are you going through?!

Technical Definition

The X-Forwarded-For header contains more than 30 IP addresses, exceeding AWS ELB's limit.

Code Snippets

Ready-to-use code for returning this HTTP status in your application:

Node.js
// Express.js
app.get('/example', (req, res) => {
  res.status(463).json({
    error: 'Too Many IPs in X-Forwarded-For',
    message: 'Your error message here'
  });
});

// Native HTTP
const http = require('http');

http.createServer((req, res) => {
  res.writeHead(463, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'Too Many IPs in X-Forwarded-For',
    message: 'Your error message here'
  }));
}).listen(3000);
Related Status Codes
๐Ÿคจ400Bad Request๐Ÿ“ฆ413Payload Too Large๐Ÿ“‹431Request Header Fields Too Large

463 Too Many IPs in X-Forwarded-For FAQ

What causes a 463 Too Many IPs in X-Forwarded-For error?

Request passed through more than 30 proxy servers. Malicious attempt to overflow the X-Forwarded-For header. Misconfigured proxy chain. Proxy loop causing IP addresses to accumulate. Attack vector attempting header manipulation. Multiple CDN/proxy layers without proper header management. Nested load balancers without header cleanup.

460 Client Closed Connection561 Unauthorized

Popular Status Codes

  • 200 OK
  • 301 Moved Permanently
  • 302 Found
  • 400 Bad Request
  • 401 Unauthorized
  • 403 Forbidden
  • 404 Not Found
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 503 Service Unavailable

Compare Codes

  • 401 vs 403
  • 301 vs 302
  • 404 vs 410
  • 500 vs 502
  • Compare any codes โ†’

Categories

  • Informational
  • Success
  • Redirection
  • Client Error
  • Server Error
  • NGINX
  • Cloudflare
  • AWS ELB
  • Microsoft IIS

Tools

  • Cheat Sheet
  • Status Code Quiz
  • URL Checker
  • API Playground
  • Blog

ยฉ 2026 SiteError.com. All rights reserved.