-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tunnel sometimes doesn't receive a DSN in the payload #4088
Comments
This should be fixed by #4031, which should be available in the next release. For now you can drop these events until we get that release out. |
Nice! Thanks 👍 |
Is this something that will be released soon? :) |
yup as part of SDK version |
Release has been cut https://www.npmjs.com/package/@sentry/browser/v/6.14.0 :) |
Environment
How do you use Sentry?
self-hosted 21.09.
Which SDK and version?
Angular SDK, maybe this issue belongs to the Angular SDK, not sure.
Steps to Reproduce
Expected Result
I expected the payload to always include the upstream DSN. But it looks like this, when the user sees a
user feedback error page:
What should I do as a tunnel here? Drop those events?
Actual Result
I would expect that every request includes a DSN in the first line, so that it can be parsed and forwarded to Sentry.
In all other cases the payload looks correct:
The text was updated successfully, but these errors were encountered: