Error map
CORS CORS: The 'Access-Control-Allow-Origin' header contains multiple values
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (9). 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 (9)
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…
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.
401 Unauthorized without WWW-Authenticate header
The server answered 401 but didn't say which authentication scheme to use.
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: 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.
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 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.
Two steps away (26)
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 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Warning: Cannot modify header information - headers already sent
You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
HTTP 428 Precondition Required
The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.
Refused to load the script because it violates the following Content Security Policy directive
The page’s Content-Security-Policy doesn’t allow that script, style, image or connection source.
JWT Expired / Invalid Token
The JSON Web Token sent with the request is expired, malformed or signed with a different key, so the API rejects it (usually wit…
OAuth 2.0 Error: invalid_grant
The authorization code, refresh token or credentials sent to the token endpoint are invalid, expired, already used or were issued…
API Error: Invalid API Key / Incorrect API key provided
The API didn’t recognise the key sent with the request — it’s wrong, revoked, from another environment, or sent in the wrong plac…
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.
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.
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: Private Network Access preflight blocked (public site calling localhost/intranet)
Chrome blocks a public website from reaching a private IP, localhost or intranet service without explicit permission.
fetch() doesn't throw on 404/500 — response.ok must be checked
The code's catch block never runs for HTTP errors, so failed requests look successful.
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: Redirect is not allowed for a preflight request
The server answered the OPTIONS preflight with a redirect, which browsers refuse to follow.
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…
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.
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…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError