Sentry-trace may cause CORS errors

[0xshellming]

Problem Statement

We initialize sentry according to the official documents whitout Setting tracingOrigins.

Sentry will add sentry-trace to HTTP-REQUEST-HEADER automatic. This operation will cause CORS Error

If user upgrade the Sentry to the Vesion without change the tracingOrigins config. This can cause serious errors.

It would be presumptuous to add http header by default config, this operation is destructive.

We recommend that sentry-trace header to be turned off by default.

---

"@sentry/browser": "^6.13.3",
"@sentry/integrations": "^6.13.3",
"@sentry/tracing": "^6.13.3"

Solution Brainstorm

We recommend that sentry-trace header to be turned off by default.

[getsentry-release]

Routing to @getsentry/team-webplatform for triage. ⏲️

[rhcarvalho]

We can definitely improve the docs by bringing tracingOrigins into code snippets earlier. Changing the default behavior requires more deliberation, as it also impacts trace propagation.

[vladanpaunovic]

@QuXiaoMing, please refer to the documentation for tracingOrigins here.

We will look for ways to improve our documentation and communicate this better.