Error map

Content-Encoding Garbled response: content compressed twice (double gzip)

HTTP · layer 2, Network

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). 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.

Content-Encoding — Garbled response: content compressed twice (double gzip) (HTTP)Content-Enc…ERR_CONTENT_DECODING_FAILED — Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED (Browser)ERR_CONTENT_DECODIN…203 — HTTP 203 Non-Authoritative Information (HTTP)203201 — HTTP 201 Created (HTTP)201202 — HTTP 202 Accepted (HTTP)202chunked — Malformed chunked encoding (invalid chunk size / premature end) (HTTP)chunked102 — HTTP 102 Processing (HTTP)102Accept-Encoding — Brotli/gzip compression not applied (large uncompressed responses) (HTTP)Accept-Encoding406 — HTTP 406 Not Acceptable (HTTP)406ERR_EMPTY_RESPONSE — Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE (Browser)ERR_EMPTY_RESPONSEERR_TOO_MANY_REDIRECTS — Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS (Browser)ERR_TOO_MANY_REDIRE…407 — HTTP 407 Proxy Authentication Required (HTTP)407304 — HTTP 304 Not Modified (HTTP)304200 — HTTP 200 OK (but something is still wrong) (HTTP)200409 — HTTP 409 Conflict (HTTP)409506 — HTTP 506 Variant Also Negotiates (HTTP)506204 — HTTP 204 No Content (HTTP)204UnhandledPromiseRejection — Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block (Node.js)UnhandledPromiseRej…await outside async — SyntaxError: await is only valid in async functions and the top level bodies of modules (JavaScript)await outside asyncAbortError — AbortError: The user aborted a request. / signal is aborted without reason (JavaScript)AbortErrornet::ERR_INCOMPLETE_CHUNKED_ENCODING — Chrome DevTools: net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) — response cut off midway (Browser)net::ERR_INCOMPLETE…CL.TE — HTTP request smuggling: Content-Length vs Transfer-Encoding mismatch (HTTP)CL.TETransfer-Encoding — Both Content-Length and Transfer-Encoding headers present (HTTP)Transfer-Encoding507 — HTTP 507 Insufficient Storage (HTTP)507100 — HTTP 100 Continue (HTTP)100103 — HTTP 103 Early Hints (HTTP)103504 — HTTP 504 Gateway Timeout (HTTP)504524 — Cloudflare Error 524: A Timeout Occurred (Cloudflare)5241200 — Cloudflare Error 1200: Cache connection limit (Cloudflare)1200

Directly related (7)

Two steps away (21)

406HTTP

HTTP 406 Not Acceptable

The server can’t produce a response in any format listed in the request’s Accept headers.

ERR_EMPTY_RESPONSEBrowser

Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE

The server accepted the connection but closed it without sending any HTTP response — a crash, timeout or misconfigured proxy on t…

ERR_TOO_MANY_REDIRECTSBrowser

Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS

The page keeps redirecting to itself or in a loop, so the browser gives up after about 20 redirects.

407HTTP

HTTP 407 Proxy Authentication Required

A proxy between you and the server requires credentials before it will forward your request.

304HTTP

HTTP 304 Not Modified

The cached copy is still valid, so the server sends no body and the client reuses its cache.

200HTTP

HTTP 200 OK (but something is still wrong)

The request succeeded at the HTTP level — yet the page is blank, the data is wrong, or an error is hidden inside the response bod…

409HTTP

HTTP 409 Conflict

The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.

506HTTP

HTTP 506 Variant Also Negotiates

The server's content-negotiation setup is circular, so it can't pick a representation.

204HTTP

HTTP 204 No Content

The request succeeded and the server intentionally sent no response body.

UnhandledPromiseRejectionNode.js

Node.js: [UnhandledPromiseRejection] — This error originated either by throwing inside of an async function without a catch block

A promise rejected and nothing handled it; since Node 15 this crashes the process.

await outside asyncJavaScript

SyntaxError: await is only valid in async functions and the top level bodies of modules

await was used inside a function that isn’t async (or in a classic, non-module script).

AbortErrorJavaScript

AbortError: The user aborted a request. / signal is aborted without reason

A fetch was cancelled through an AbortController (or the browser cancelled it).

net::ERR_INCOMPLETE_CHUNKED_ENCODINGBrowser

Chrome DevTools: net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) — response cut off midway

The server started sending a chunked response with status 200 and then stopped before the final chunk, so Chrome reports the tran…

CL.TEHTTP

HTTP request smuggling: Content-Length vs Transfer-Encoding mismatch

Two servers in a chain disagree about where a request ends, letting an attacker hide a second request inside the first.

Transfer-EncodingHTTP

Both Content-Length and Transfer-Encoding headers present

A message has both framing headers, which HTTP says a sender must not do.

507HTTP

HTTP 507 Insufficient Storage

The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.

100HTTP

HTTP 100 Continue

An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.

103HTTP

HTTP 103 Early Hints

An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server is still buil…

504HTTP

HTTP 504 Gateway Timeout

A proxy or gateway waited too long for the upstream server to respond and gave up.

524Cloudflare

Cloudflare Error 524: A Timeout Occurred

Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.

1200Cloudflare

Cloudflare Error 1200: Cache connection limit

Too many requests are queued at Cloudflare for the origin — the origin is slow and connections pile up.