HTTPError.net

The fastest way to diagnose, understand, and fix any HTTP status code

414 URI Too Long

Fault: Client
TL;DR

URL is too long for the server to process.

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

What This Error 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

How to Fix It (For Visitors)

How to Fix It (For Developers/Admins)

Code Examples

Here's how to return a 414 status code in various programming languages:

Python (Flask)

from flask import Flask, jsonify

app = Flask(__name__)

@app.route('/endpoint')
def endpoint():
    return jsonify({"message": "URI Too Long"}), 414

Node.js (Express)

const express = require('express');
const app = express();

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

PHP

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

Go

package main

import (
    "encoding/json"
    "net/http"
)

func handler(w http.ResponseWriter, r *http.Request) {
    w.Header().Set("Content-Type", "application/json")
    w.WriteHeader(414)
    json.NewEncoder(w).Encode(map[string]string{
        "message": "URI Too Long",
    })
}

Java (Spring Boot)

@GetMapping("/endpoint")
public ResponseEntity<Map<String, String>> endpoint() {
    Map<String, String> response = new HashMap<>();
    response.put("message", "URI Too Long");
    return ResponseEntity.status(414).body(response);
}

Ruby (Sinatra)

get '/endpoint' do
    status 414
    json message: 'URI Too Long'
end

Browser Compatibility

Browser Support Notes
Chrome✓ Full SupportAll versions
Firefox✓ Full SupportAll versions
Safari✓ Full SupportAll versions
Edge✓ Full SupportAll versions

Official Specification

This status code is defined in RFC 7231 Section 6.5.12.

View on IANA HTTP Status Code Registry →