-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
User Feedback submission CORS error: Request header field baggage is not allowed by Access-Control-Allow-Headers in preflight response #8823
Comments
This looks like a similar issue to #6077 Upon further investigation, I was setting |
Hi there. Nothing prevents sentry from adding the baggage on my case, I've tried adding:
I'm using sentry {
"@sentry/browser": "7.9.0",
"@sentry/integrations": "7.9.0",
"@sentry/nextjs": "7.9.0",
"@sentry/react": "7.9.0",
} My client side config is init({
// my dsn as string
dsn: SENTRY_DSN || '***',
// Adjust this value in production, or use tracesSampler for greater control
environment: SENTRY_ENVIRONMENT,
normalizeDepth: 11,
integrations: [new ExtraErrorData({ depth: 10 })],
tracePropagationTargets: [],
tracesSampleRate: 0,
tracesSampler: () => 0,
// ...
ignoreErrors: [/^Product not found for sku: ([\w]*)$/],
}) It seems like it doesn't add the sentry-trace but still breaks THIRD_PARTY CORS> Any help would be much appreciated. |
@pelagaggi I have the same exact issue and also on |
same issue here |
Confirming this is still an issue |
Same issue here |
same here |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/vue
SDK Version
7.64.0
Framework Version
7.64.0
Link to Sentry event
https://sentry.io/api/embed/error-page/?dsn=https://1d71f704d08d4bad95a66d041a087279@o4505162248945664.ingest.sentry.io/4505517755138048&eventId=483fc1b01e0545c087b10949a364a861
SDK Setup
Steps to Reproduce
Sentry.showReportDialog
Expected Result
Successful submission
Actual Result
Baggage
andSentry-Trace
are indeed in the outgoing request (as I believe they should be).But the response for the OPTIONS request doesn't include them in
Access-Control-Allow-Headers
:The text was updated successfully, but these errors were encountered: