403 (FORBIDDEN): Event dropped due to filter, on basic use case
See original GitHub issueEntering this in the console:
Raven.config('https://<key>@sentry.io/<key>').install()
try{
throw new Error('test');
} catch(err){
console.log('err', err);
Raven.captureException(err);
}
returns:
(with the reponse message being Event dropped due to filter
)
Versions:
- “raven”: “2.2.1”,
- “raven-js”: “^3.19.1”,
I had initially reported it here
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
403 Forbidden Error: What Is It & How To Fix It
A 403 error status code will be triggered when your previous host terminates your account.
Read more >What Is the 403 Forbidden Error and How to Fix It (8 Methods ...
There are two possibilities in this case: either the website owner edited the settings so that you couldn't access the resources, or they...
Read more >403 Forbidden Error: What It Is and How to Fix It - Airbrake Blog
A detailed explanation of what a 403 Forbidden Error response is, including troubleshooting tips to help you resolve this error.
Read more >How to Fix WordPress 403 Forbidden Error - 7 Simple Ways
1. Clear Your Browsing Cache. Clearing your browser's cache is the simplest solution to the 403 error, and a hard refresh is always...
Read more >How to Fix a 403 Forbidden Error on Your WordPress Site
The 403 Forbidden error indicates that the server understood the request but refuses to authorize it. Find out more about the causes and ......
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
I had the same issue today. In case someone can’t figure it out you have you add
localhost
to “Allowed Domains”. I’d suggest removing it as soon as you end testing 😉After many experiments I have found that this happens when Header > Referer is
http://localhost:*