403 when origin is null
See original GitHub issueI’m developing a web app for Samsung Smart TV. It uses local file protocol, other than normal http. When sentry catches some error and sends to server, there is a 403 response, with the following body:
{
"error": "Missing required attribute in authentication header: sentry_secret"
}
I checked the request header, found that origin
header is null
. When assigning a valid origin in postman, such like ‘abc.com’, it’s ok.
My question is, how can I fix this issue? change origin settings in sentry, or generate a private DSN?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
HTTP 403 Error Solution - Access-Control-Allow-Origin
In this post, you will get to know about the Http 403 error, No 'Access-Control-Allow-Origin' header, and how to fix this problem.
Read more >Origin null is not allowed by Access-Control-Allow-Origin
But I am getting the following error: Origin null is not allowed by Access-Control-Allow-Origin. I've read about adding a header to the xslt, ......
Read more >Troubleshooting Access-control-allow-origin error 403 - AskF5
Support Solution. The origin making the request does not match any of the origins permitted by the Access-control-allow-origin header. Access- ...
Read more >HTTPRequest Origin="null" - The Observable Forum
Chrome and Safari has a restriction on using ajax with local resources. This error means that you are trying to perform Ajax on...
Read more >Reason: CORS header 'Access-Control-Allow-Origin' missing
The response to the CORS request is missing the required Access-Control-Allow-Origin header, which is used to determine whether or not the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
To fix my issue, I had to force using XHRTransport:
Hey, sorry for the inconvenience @y-lohse. We’re working on the next major version right now and we’ll make sure that it won’t create issues like the one you described above.