Back to list
414

URI Too Long

4xx Client Error

.md

ELI5

The web address (URL) you're using is too long for me to handle. Please make it shorter or use a different method.

Server perspective

Use 414 when the request target URI is longer than the server is willing to interpret.

When to use

  • •Return 414 for oversized query strings, paths, or encoded request targets
  • •Use it when the problem is the request-target itself rather than the body or headers
  • •URL exceeds server's length limits
  • •Query strings with too many parameters
  • •Very long paths or resource identifiers
  • •URLs with excessive encoded characters

How to respond

  • •Document URI length constraints when clients commonly generate long filter or search URLs
  • •Recommend POST or another request shape if the workflow naturally exceeds safe URI lengths

Headers to consider

  • •No status-specific header is required; still send normal HTTP metadata such as Content-Type, caching, or tracing headers when they help the client.

Response body

  • •Optionally explain the URI length limit or point clients to a POST/search endpoint when one exists.

Server-side pitfalls

  • •Do not use 414 for oversized headers or bodies
  • •Do not let unbounded client-generated query strings grow without guardrails
  • •Request body too large (use 413 Content Too Large)
  • •Headers too large (use 431 Request Header Fields Too Large)
  • •Bad URL format (use 400 Bad Request)

Examples

Query string too long

Request:GET https://api.example.test/api/search
Response:414 URI Too Long # Headers Content-Type: application/json # Body { "error": "uri_too_long" }

Query parameters exceed server's URL length limit

References

Related Status Codes

400

Bad Request

Your request doesn't make sense or has mistakes in it. Check what you're sending and try again.

413

Content Too Large

The file or data you're trying to send is too big for me to handle. Please make it smaller.