Error map
Content-Encoding Garbled response: content compressed twice (double gzip)
HTTP · layer 2, Network
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.
Directly related (7)
Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED
The response claims to be compressed (gzip/brotli) but cannot be decompressed — it was double-compressed, truncated or not compre…
HTTP 203 Non-Authoritative Information
The request worked, but a proxy changed the response, so the content may differ from the origin's.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
HTTP 202 Accepted
The server accepted the request for processing, but the work is not finished yet.
Malformed chunked encoding (invalid chunk size / premature end)
The body claims to use chunked transfer encoding, but the chunk sizes or terminator are wrong.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
Brotli/gzip compression not applied (large uncompressed responses)
Responses are sent uncompressed, so pages are slower and bandwidth higher than necessary.
Two steps away (21)
HTTP 406 Not Acceptable
The server can’t produce a response in any format listed in the request’s Accept headers.
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…
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.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
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…
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.
HTTP 506 Variant Also Negotiates
The server's content-negotiation setup is circular, so it can't pick a representation.
HTTP 204 No Content
The request succeeded and the server intentionally sent no response body.
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.
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).
AbortError: The user aborted a request. / signal is aborted without reason
A fetch was cancelled through an AbortController (or the browser cancelled it).
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…
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.
Both Content-Length and Transfer-Encoding headers present
A message has both framing headers, which HTTP says a sender must not do.
HTTP 507 Insufficient Storage
The server can’t store what’s needed to complete the request — the disk, quota or mailbox is full.
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.
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…
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
Cloudflare Error 1200: Cache connection limit
Too many requests are queued at Cloudflare for the origin — the origin is slow and connections pile up.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError