Error map
ETag Conditional requests always return 200 (ETag/Last-Modified never matches)
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (8). 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 (8)
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
404 on JS/CSS assets after a new deploy
The page loads old HTML that points to hashed asset files the new deploy removed.
CDN or browser serving stale content after a deploy
Users still see the old CSS, JS or HTML after you released a new version.
Cache hit rate collapses: Vary: Cookie or Vary: * on responses
A Vary header makes caches store a separate copy per cookie or header value, so almost nothing is served from cache.
CORS responses cached for the wrong origin (missing Vary: Origin)
A cache or CDN stored a CORS response for one origin and served it to another, so some sites get blocked.
CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response
The response tells shared caches not to store it, so the CDN passes every request to your origin.
Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back)
Pressing Back reloads the page from scratch instead of restoring it instantly, or shows stale/old data.
Resumed download restarts from zero (If-Range validator mismatch)
A download manager tries to resume, but the server sends the full file again because the validator no longer matches.
Two steps away (19)
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.
HTTP 412 Precondition Failed
A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.
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 404 Not Found
The server can’t find anything at the requested URL.
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
Laravel: Illuminate\Database\Eloquent\ModelNotFoundException: No query results for model [App\Models\Post] 5
`findOrFail`, `firstOrFail` or route-model binding couldn't find a record, so Laravel returns a 404.
Cloudflare Error 520: Web Server Returned an Unknown Error
Cloudflare connected to your origin, but the origin returned an empty, unknown or invalid response.
CloudFront: 403 ERROR — The request could not be satisfied
CloudFront refused or couldn’t serve the request — wrong alternate domain/certificate, blocked by origin access settings, a WAF/g…
Cloudflare not caching: cf-cache-status DYNAMIC / BYPASS / MISS every time
Cloudflare isn’t caching the response — HTML isn’t cached by default, and cookies or Cache-Control headers from the origin preven…
Brotli/gzip compression not applied (large uncompressed responses)
Responses are sent uncompressed, so pages are slower and bandwidth higher than necessary.
Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode
Responses keep missing the CDN cache, so every request reaches the origin.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
405 Method Not Allowed on OPTIONS (CORS preflight)
The browser's CORS preflight (OPTIONS) request is rejected, so the real request never gets sent.
CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses
The browser reports a CORS error, but the real problem is a server error (500, 401, 404) whose response carries no CORS headers.
Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")
You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.
ERR_CACHE_MISS: Confirm Form Resubmission
You pressed Back/Refresh on a page that was the result of a form POST, so the browser asks before sending the form again.
HTTP 102 Processing
An interim WebDAV response saying the server accepted a long-running request and is still working on it.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
HTTP 206 Partial Content
The server returned only the byte range the client asked for with a Range header.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError