Skip to content
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

feat: Add tracePropagationTargets option #1396

Merged
merged 1 commit into from
Oct 4, 2022

Conversation

cleptric
Copy link
Member

@cleptric cleptric commented Oct 4, 2022

To not break people's usage of the GuzzleTracingMiddleware, I only check for tracePropagationTargets when applying the baggage header.

Also nothing fancy here, a simple array with an allow-list of hosts.

Closes #1395 & #1361

@cleptric cleptric added this to the 3.9 milestone Oct 4, 2022
@cleptric cleptric self-assigned this Oct 4, 2022
@cleptric cleptric marked this pull request as ready for review October 4, 2022 14:51
@cleptric cleptric linked an issue Oct 4, 2022 that may be closed by this pull request
@cleptric cleptric merged commit 2e7607d into develop Oct 4, 2022
@cleptric cleptric deleted the trace-propagation-targets branch October 4, 2022 15:58
absumo added a commit to sumocoders/application-skeleton that referenced this pull request Sep 19, 2023
Sending the baggage header might result in errors from external APIs
and can potentially leak private data.

This limits the trace_propagation_targets to only the current domain.
An empty array (the default when not set) is treated as all hosts are allow listed.

See this PR for additional info: getsentry/sentry-php#1396
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add tracePropagationTargets option
2 participants