Request header field X-CSRF-TOKEN is not allowed by Access-Control-Allow-Headers in preflight response
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 496
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
I'm unable to use noembed on my website due to the error:
Request header field X-CSRF-TOKEN is not allowed by Access-Control-Allow-Headers in preflight response
I've updated my server's CORS settings to include "X-CSRF-Token" but it doesn't appear to be making a difference. Please advise.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the reported browser preflight request against noembed and inspect the service's CORS response behavior. Done means requests containing X-CSRF-TOKEN receive an Access-Control-Allow-Headers response that permits the header, or the issue is clarified with the relevant server configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100