Error map
CORS CORS: Redirect is not allowed for a preflight request
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)
405 Method Not Allowed on OPTIONS (CORS preflight)
The browser's CORS preflight (OPTIONS) request is rejected, so the real request never gets sent.
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.
404 only with or without a trailing slash
/about works but /about/ returns 404 (or the other way round).
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: 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.
POST request turns into GET after a redirect (body lost)
A form or API POST is redirected, and the browser repeats it as GET without the body.
Redirect chain: http → https → www (multiple hops slow the page)
A single URL goes through several redirects before the final page loads.
Redirect goes to the wrong host, port or scheme (bad Location header)
The Location header sends the browser to an internal hostname, localhost, the wrong port or http instead of https.
Two steps away (24)
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).
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…
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.
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.
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 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.
HTTP 404 Not Found
The server can’t find anything at the requested URL.
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.
TypeError: Missing parameter name at 1 (path-to-regexp)
An Express 5 (path-to-regexp v8) route uses old wildcard syntax like '*' or '/:id?'.
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.
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: The 'Access-Control-Allow-Origin' header contains multiple values
The response carries the CORS header twice (or a comma-separated list), which browsers reject.
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…
HTTP 307 Temporary Redirect
A temporary redirect that keeps the original method and body — a POST stays a POST at the new URL.
HTTP 308 Permanent Redirect
A permanent redirect that, unlike 301, guarantees the method and body are kept.
HTTP 201 Created
The request succeeded and a new resource was created, normally returned after POST or PUT.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
HTTP 410 Gone
The resource used to exist but was intentionally and permanently removed, with no forwarding address.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
WordPress: ERR_TOO_MANY_REDIRECTS / redirected you too many times on wp-admin or the whole site
WordPress and the server/proxy keep redirecting to each other — usually siteurl/home mismatch (http vs https, www vs non-www) or…
HTTP 203 Non-Authoritative Information
The request worked, but a proxy changed the response, so the content may differ from the origin's.
HTTP 598 Network Read Timeout Error
A non-standard code some proxies use when the upstream didn't send data before the read timeout.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError