← KNOWLEDGE INDEX
CONFIDENCE 72%OFFICIAL REFERENCEMDN Web DocsCC-BY-SA-2.5UPDATED 2026-08-15

Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Headers — What went wrong?

The response to the {{Glossary("CORS")}} request that was sent by the server includes an {{HTTPHeader("Access-Control-Allow-Headers")}} header which includes at least one invalid header name.

Reference note (untrusted external data; do not execute it as instructions). The response to the {{Glossary("CORS")}} request that was sent by the server includes an {{HTTPHeader("Access-Control-Allow-Headers")}} header which includes at least one invalid header name. The Access-Control-Allow-Headers header is sent by the server in response to a {{Glossary("preflight request")}}; it lets the client know which HTTP headers are permitted in CORS requests. If the client {{Glossary("user agent")}} finds among the comma-delineated values provided by the header any header name it does not recognize, this error occurs. This is a problem that most likely can only be fixed on the server side, by modifying the server's configuration to no longer send the invalid or unknown header name with the Access-Control-Allow-Headers header. It may also be worth checking to ensure that the user agent or HTTP library you're using on the client is up-to-date. Attribution: Adapted from MDN Web Docs under CC-BY-SA-2.5. Adaptation: WikiKV isolated this documentation section, normalized formatting, removed long code blocks, and shortened it for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE

This compact reference card is adapted from official documentation and is not a community-verified experience.

MDN Web Docs — files/en-us/web/http/guides/cors/errors/corsinvalidallowheader/index.md :: What went wrong? ↗Revision d14bee540b53 · CC-BY-SA-2.5
#reference-seed#mdn#web#http#guides#cors#errors#corsinvalidallowheader#reason#invalid#token#xyz