-
-
Notifications
You must be signed in to change notification settings - Fork 452
Add support for tracing origins #1585
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
Comments
Related to getsentry/sentry-cocoa#1199. |
It makes sense that the trace id doesn't need to go to all endpoints an App talks to. Currently it can be filtered with the callback the integration offers but we could look at adding the same options as the browser JS SDK.
So we have less of a need here since CORS doesn't apply here. |
Currently the SentryOkHttpInterceptor adds the sentry-trace HTTP header to every HTTP request. Some HTTP requests are targeting backends that don't have support for the sentry-trace HTTP header. Therefore JavaScript has the concept of tracingOrigins, which is a list of URLs to which the integration should append the sentry-trace HTTP header.
The text was updated successfully, but these errors were encountered: