SiteError.comYour friendly guide to HTTP status codes
Status CodesBlog
  1. Home
  2. 4xx Client Error
  3. 414 URI Too Long

414 URI Too Long

📜
414
URI Too Long
!
?

Example HTTP Response

HTTP Response
HTTP/1.1 414 URI Too Long
Common Causes
  • Too many query parameters
  • Accidentally recursive redirects
  • Encoded data in URL instead of body
Technical Details

What does this mean?

That URL is a novel! Like trying to write your life story on a sticky note. Keep it short and sweet!

Technical Definition

The URI requested by the client is longer than the server is willing to interpret.

RFC Says

"The 414 (URI Too Long) status code indicates that the server is refusing to service the request because the request-target is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information."

Plain English:

414 means 'Your URL is too long.' This usually happens when developers try to pass too much data in query parameters. The typical limit is around 2,000-8,000 characters depending on the server.

Common Misinterpretation

If you're hitting this error, you're probably doing something wrong architecturally. Use POST requests with a request body instead of GET with massive query strings. Don't try to pass large datasets or complex objects in the URL.

View RFC Documentation
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(414).json({
    error: 'URI Too Long',
    message: 'Your error message here'
  });
});

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

http.createServer((req, res) => {
  res.writeHead(414, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'URI Too Long',
    message: 'Your error message here'
  }));
}).listen(3000);

414 URI Too Long FAQ

What causes a 414 URI Too Long error?

Too many query parameters. Accidentally recursive redirects. Encoded data in URL instead of body.

413 Payload Too Large415 Unsupported Media Type

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.