Error map

414 HTTP 414 URI Too Long

HTTP · layer 2, Network

Open the full error page →

Centre: this error. First ring: errors it is linked with (3). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

2 · Network 3 · Edge & web server 4 · Application & API
414 — HTTP 414 URI Too Long (HTTP)414400 — HTTP 400 Bad Request (HTTP)400301 — HTTP 301 Moved Permanently (HTTP)301431 — HTTP 431 Request Header Fields Too Large (HTTP)431401 — HTTP 401 Unauthorized (HTTP)401405 — HTTP 405 Method Not Allowed (HTTP)405413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413404 — HTTP 404 Not Found (HTTP)404410 — HTTP 410 Gone (HTTP)410520 — Cloudflare Error 520: Web Server Returned an Unknown Error (Cloudflare)520Cookies are blocked — WordPress login: Error: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress. (WordPress)Cookies are blockedlogin_required — OIDC Error: login_required / interaction_required / consent_required (silent authentication failed) (Authentication)login_requiredstate mismatch — OAuth callback error: state mismatch / Unable to verify authorization request state / State cookie was missing (Authentication)state mismatch

Directly related (3)

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

301HTTP

HTTP 301 Moved Permanently

The resource has a new permanent URL; clients and search engines should use the address in the Location header from now on.

431HTTP

HTTP 431 Request Header Fields Too Large

The request headers — almost always cookies — exceed the server’s size limit.

Two steps away (9)

401HTTP

HTTP 401 Unauthorized

The request has no valid authentication credentials — you need to log in or send a valid token.

405HTTP

HTTP 405 Method Not Allowed

The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).

413HTTP

HTTP 413 Content Too Large (Request Entity Too Large)

The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.

404HTTP

HTTP 404 Not Found

The server can’t find anything at the requested URL.

410HTTP

HTTP 410 Gone

The resource used to exist but was intentionally and permanently removed, with no forwarding address.

520Cloudflare

Cloudflare Error 520: Web Server Returned an Unknown Error

Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.

Cookies are blockedWordPress

WordPress login: Error: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.

WordPress’s test cookie wasn’t returned on login — often a siteurl/home or domain mismatch, caching of wp-login.php, or headers a…

login_requiredAuthentication

OIDC Error: login_required / interaction_required / consent_required (silent authentication failed)

A silent sign-in (prompt=none, iframe or refresh) couldn’t complete because the user must interact — no session, consent needed,…

state mismatchAuthentication

OAuth callback error: state mismatch / Unable to verify authorization request state / State cookie was missing

The state value returned to the callback doesn’t match what the app stored before redirecting — the CSRF protection for OAuth fai…

Map another error

Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException