feat(http): [Data Collection 11] Apply response header policy#5807
Draft
adinauer wants to merge 2 commits into
Draft
feat(http): [Data Collection 11] Apply response header policy#5807adinauer wants to merge 2 commits into
adinauer wants to merge 2 commits into
Conversation
Filter automatically collected response headers through the Data Collection policy in OkHttp, Ktor, and Apollo failed-request events. Preserve sendDefaultPii behavior when Data Collection is absent. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
|
This was referenced Jul 21, 2026
📲 Install BuildsAndroid
|
Contributor
Performance metrics 🚀
|
Bring the queue option removal and preceding stack updates into this layer.
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
Sign up for free
to 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.
PR Stack (Data Collection)
📜 Description
Apply the response-header Data Collection policy to OkHttp, Ktor, and Apollo 3/4 failed-request events.
Explicit Data Collection supports off, deny-list, and allow-list behavior with canonical sensitive-key filtering. When Data Collection is absent,
sendDefaultPii=falsecontinues to omit response headers andsendDefaultPii=truecontinues to collect headers while omitting legacy-sensitive names.💡 Motivation and Context
These are the current global response-header consumers. Central filtering provides granular response-header control while preserving historical behavior for applications that have not opted into Data Collection. Session Replay network headers remain governed by Replay-specific integration controls.
Refs #5666
💚 How did you test it?
./gradlew spotlessApply apiDumpgit diff --check📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Migrate cookie and query-parameter collection and coordinate Replay inheritance from global Data Collection policies.
#skip-changelog