Error map

ETag Conditional requests always return 200 (ETag/Last-Modified never matches)

HTTP · layer 2, Network

Open the full error page →

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.

ETag — Conditional requests always return 200 (ETag/Last-Modified never matches) (HTTP)ETag304 — HTTP 304 Not Modified (HTTP)304404 — 404 on JS/CSS assets after a new deploy (HTTP)404CDN cache — CDN or browser serving stale content after a deploy (HTTP)CDN cacheVary — Cache hit rate collapses: Vary: Cookie or Vary: * on responses (HTTP)VaryVary: Origin — CORS responses cached for the wrong origin (missing Vary: Origin) (HTTP)Vary: OriginCache-Control — CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response (HTTP)Cache-ControlCache-Control — Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back) (HTTP)Cache-ControlIf-Range — Resumed download restarts from zero (If-Range validator mismatch) (HTTP)If-Range301 — HTTP 301 Moved Permanently (HTTP)301412 — HTTP 412 Precondition Failed (HTTP)412200 — HTTP 200 OK (but something is still wrong) (HTTP)200404 — HTTP 404 Not Found (HTTP)404ChunkLoadError — ChunkLoadError: Loading chunk 123 failed. (JavaScript)ChunkLoadErrorNo query results for model — Laravel: Illuminate\Database\Eloquent\ModelNotFoundException: No query results for model [App\Models\Post] 5 (Laravel)No query results fo…520 — Cloudflare Error 520: Web Server Returned an Unknown Error (Cloudflare)520The request could not be satisfied — CloudFront: 403 ERROR — The request could not be satisfied (AWS)The request could n…cf-cache-status: DYNAMIC — Cloudflare not caching: cf-cache-status DYNAMIC / BYPASS / MISS every time (Cloudflare)cf-cache-status: DY…Accept-Encoding — Brotli/gzip compression not applied (large uncompressed responses) (HTTP)Accept-EncodingCloud CDN — Cloud CDN not caching: cache misses because of Set-Cookie, Cache-Control or missing cache mode (Google Cloud / Firebase)Cloud CDNCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORS405 — 405 Method Not Allowed on OPTIONS (CORS preflight) (HTTP)405CORS on errors — CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses (HTTP)CORS on errorsDomain still resolves to the old IP (DNS propagation/cache) — Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation") (Networking)Domain still resolv…ERR_CACHE_MISS — ERR_CACHE_MISS: Confirm Form Resubmission (Browser)ERR_CACHE_MISS102 — HTTP 102 Processing (HTTP)102201 — HTTP 201 Created (HTTP)201206 — HTTP 206 Partial Content (HTTP)206

Directly related (8)

Two steps away (19)

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.

412HTTP

HTTP 412 Precondition Failed

A conditional request header (If-Match, If-Unmodified-Since) didn’t match the current state of the resource.

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…

404HTTP

HTTP 404 Not Found

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

ChunkLoadErrorJavaScript

ChunkLoadError: Loading chunk 123 failed.

A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.

No query results for modelLaravel

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.

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.

The request could not be satisfiedAWS

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…

cf-cache-status: DYNAMICCloudflare

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…

Accept-EncodingHTTP

Brotli/gzip compression not applied (large uncompressed responses)

Responses are sent uncompressed, so pages are slower and bandwidth higher than necessary.

Cloud CDNGoogle Cloud / Firebase

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.

CORSAPI

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…

405HTTP

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 on errorsHTTP

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.

Domain still resolves to the old IP (DNS propagation/cache)Networking

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_MISSBrowser

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.

102HTTP

HTTP 102 Processing

An interim WebDAV response saying the server accepted a long-running request and is still working on it.

201HTTP

HTTP 201 Created

The request succeeded and a new resource was created, normally returned after POST or PUT.

206HTTP

HTTP 206 Partial Content

The server returned only the byte range the client asked for with a Range header.