feat: Implement strict_trace_continuation#5178
Merged
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
sl0thentr0py changed the title 
sl0thentr0pyforce-pushed the neel/strict-trace-continuation branch from 6ff62ad to 290a89dCompare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## master #5178 +/- ## ======================================= Coverage 83.92% 83.92% ======================================= Files 181 181 Lines 18340 18357 +17 Branches 3260 3264 +4 ======================================= + Hits 15391 15406 +15 - Misses 1941 1944 +3 + Partials 1008 1007 -1
|
6 tasks
Uh oh!
There was an error while loading. Please reload this page.
sl0thentr0pyforce-pushed the neel/strict-trace-continuation branch 2 times, most recently from 445f508 to 12f82c8Compare
Fixes a security hole where incoming traces from other orgs can cause a DOS-like attack on another org by injecting Sentry propagation headers. Spec: https://develop.sentry.dev/sdk/telemetry/traces/#stricttracecontinuation
sl0thentr0pyforce-pushed the neel/strict-trace-continuation branch from 12f82c8 to aedff10Compare
alexander-alderman-webb approved these changes Dec 1, 2025
sl0thentr0py merged commit 9aa4385 into master 155 checks passed
Uh oh!
There was an error while loading. Please reload this page.
sl0thentr0py added a commit to getsentry/sentry-docs that referenced this pull request Dec 1, 2025
## DESCRIBE YOUR PR goes with getsentry/sentry-python#5178 preview: https://sentry-docs-git-neel-python-strict-trace.sentry.dev/platforms/python/configuration/options/#strict_trace_continuation ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [x] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Alex Alderman Webb <alexander.webb@sentry.io>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes a security hole where incoming traces from other orgs can cause a DOS-like attack on another org by injecting Sentry propagation headers.
Spec: https://develop.sentry.dev/sdk/telemetry/traces/#stricttracecontinuation
Issues