Error map
Vary: Origin CORS responses cached for the wrong origin (missing Vary: Origin)
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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…
404 on JS/CSS assets after a new deploy
The page loads old HTML that points to hashed asset files the new deploy removed.
405 Method Not Allowed on OPTIONS (CORS preflight)
The browser's CORS preflight (OPTIONS) request is rejected, so the real request never gets sent.
CDN or browser serving stale content after a deploy
Users still see the old CSS, JS or HTML after you released a new version.
Conditional requests always return 200 (ETag/Last-Modified never matches)
The client sends If-None-Match or If-Modified-Since, but the server never answers 304, so the full body is re-downloaded every ti…
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.
Axios "Network Error" with no response (CORS, DNS, offline or mixed content)
Axios shows a generic Network Error and `error.response` is undefined, so there is no status code to inspect.
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.
CORS: wildcard '*' not allowed when the request's credentials mode is 'include'
The server answered `Access-Control-Allow-Origin: *`, but credentialed requests (cookies, Authorization) require an exact origin.
CORS: The 'Access-Control-Allow-Origin' header contains multiple values
The response carries the CORS header twice (or a comma-separated list), which browsers reject.
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.
Two steps away (28)
AWS S3: AccessDenied (403) when calling GetObject / PutObject
An IAM policy, bucket policy, ACL/ownership setting, Block Public Access or KMS key policy denied the S3 request.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
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.
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).
Console: SecurityError: Failed to execute 'toDataURL' / 'getImageData' on 'HTMLCanvasElement': Tainted canvases may not be exported
You drew an image from another origin onto a canvas without CORS permission, so the browser blocks reading pixels back out.
Browser: Access to XMLHttpRequest at 'https://api.example.com' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header — Laravel
The browser blocked a cross-origin call to your Laravel API because the response lacks the right CORS headers.
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…
HTTP 304 Not Modified
The cached copy is still valid, so the server sends no body and the client reuses its cache.
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.
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.
Mixed Content: The page was loaded over HTTPS, but requested an insecure resource
An HTTPS page tried to load a script, API or image over plain HTTP, and the browser blocked (or warned about) it.
CORS: Response to preflight request doesn't pass access control check: no HTTP ok status
The browser's OPTIONS preflight got an error status (401, 403, 404, 405, 500) instead of 2xx.
CORS: Redirect is not allowed for a preflight request
The server answered the OPTIONS preflight with a redirect, which browsers refuse to follow.
400 Bad Request: Request Header Or Cookie Too Large
The server rejected the request because its headers, usually accumulated cookies, are bigger than it allows.
400 Bad Request: invalid character in header
A header contains a character the HTTP parser doesn't accept, such as a newline, a null byte or raw non-ASCII text.
CORS: Request header field is not allowed by Access-Control-Allow-Headers in preflight response
Your request adds a custom header (Authorization, X-Api-Key, Content-Type: application/json) the server didn't list as allowed.
AWS: ExpiredToken — The security token included in the request is expired
Temporary AWS credentials (STS/SSO/assumed role) have expired.
AWS: Unable to locate credentials / Could not load credentials from any providers
The AWS CLI/SDK found no credentials in any place it looks — env vars, profile files, SSO cache or an instance/task role.
AWS: SignatureDoesNotMatch / InvalidClientTokenId — the request signature we calculated does not match
AWS rejected the request signature — wrong secret key, wrong region, clock skew, or a presigned URL used differently from how it…
401 Unauthorized without WWW-Authenticate header
The server answered 401 but didn't say which authentication scheme to use.
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.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError