Part of #5420. Phase 0 — hardening pre-work, no new public API.
Query strings are captured unconditionally and unscrubbed today:
src/Sentry.AspNetCore/ScopeExtensions.cs:136 — scope.Request.QueryString = context.Request.QueryStringsrc/Sentry.AspNet/Internal/SystemWebRequestEventProcessor.cs:50
Apply the sensitive-terms denylist to query parameter values (keys preserved, values → [Filtered]; unparseable query string → [Filtered] wholesale). This is privacy hardening in its own right — an ?access_token=... or ?session_id=... currently reaches Sentry in clear text.
Depends on the denylist/filter utility issue.
Part of #5420. Phase 0 — hardening pre-work, no new public API.
Query strings are captured unconditionally and unscrubbed today:
src/Sentry.AspNetCore/ScopeExtensions.cs:136—scope.Request.QueryString = context.Request.QueryStringsrc/Sentry.AspNet/Internal/SystemWebRequestEventProcessor.cs:50Apply the sensitive-terms denylist to query parameter values (keys preserved, values →
[Filtered]; unparseable query string →[Filtered]wholesale). This is privacy hardening in its own right — an?access_token=...or?session_id=...currently reaches Sentry in clear text.Depends on the denylist/filter utility issue.