414 URI Too Long

What HTTP 414 URI Too Long Means

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

URL is too long for the server to process.

Common Causes

• Excessive query parameters
• Very long URL
• Too much data in GET request

How to Fix It (For Visitors)

• Use shorter URL
• Contact website support

How to Fix It (For Developers/Admins)

• Use POST instead of GET for large data
• Reduce query parameters
• Increase LimitRequestLine (Apache)
• Use request body for large payloads

Returning a 414 URI Too Long (Code Examples)

If you build APIs or web apps, here is how to send an HTTP 414 response and how to test for it:

Node.js (Express)

app.get('/resource', (req, res) => {
  res.status(414).json({ error: 'URI Too Long' });
});

Python (Flask)

@app.route('/resource')
def resource():
    return jsonify(error='URI Too Long'), 414

PHP

<?php
http_response_code(414);
header('Content-Type: application/json');
echo json_encode(['error' => 'URI Too Long']);

Check the status with curl

curl -I https://example.com/resource
# Look for: HTTP/1.1 414 URI Too Long

Frequently Asked Questions

What does HTTP 414 URI Too Long mean?

URL is too long for the server to process. In short: The URI requested by the client is longer than the server is willing to interpret.

Is 414 URI Too Long a client or server error?

414 is a 4xx client-error code, so the request itself needs to change. The server is running normally and is rejecting the request as it was sent by the browser, app, or API client.

How do I fix a 414 URI Too Long error?

Use POST instead of GET for large data. Reduce query parameters. Increase LimitRequestLine (Apache).

Official Specification

The 414 URI Too Long status code is defined in RFC 7231 Section 6.5.12.

View the IANA HTTP Status Code Registry →