| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
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>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
Performance metrics 🚀
Baseline results on branch: feat/data-collection-http-request-headersStartup times
App size
Previous results on branch: feat/data-collection-http-response-headersStartup times
App size
|
Sorry, something went wrong.
Bring the queue option removal and preceding stack updates into this layer.
…ta-collection-http-response-headers
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
Sorry, something went wrong.
…ta-collection-http-response-headers
Verify Apollo 4 applies deny-list behavior to response headers for both supported execution implementations. Co-Authored-By: Claude <noreply@anthropic.com>
…ta-collection-http-response-headers
…ta-collection-http-response-headers
…ta-collection-http-response-headers
…ta-collection-http-response-headers
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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=false continues to omit response headers and sendDefaultPii=true continues 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?
📝 Checklist
🔮 Next steps
Migrate cookie and query-parameter collection. Document that Session Replay remains governed by Replay-specific privacy controls.
#skip-changelog