Repository navigation
fix(browser): Apply urlQueryParams to breadcrumb and element timing URLs - #25289
Conversation
… URLs The fetch, XHR and navigation breadcrumbs and the `ui.element.url` attribute of `elementTimingIntegration` still sent sensitive query values such as `?token=...` to Sentry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
bugbot run |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1aa2891. Configure here.
| from, | ||
| to, | ||
| from: filterCollectedUrl(from), | ||
| to: filterCollectedUrl(to), |
There was a problem hiding this comment.
filterCollectedUrl omits in-scope client
Low Severity
This is more an "is this necessary" check than a functional break: filterCollectedUrl is called without the in-scope client, so it falls back to getClient(). The review guidelines ask to pass the client when one is available so dataCollection.urlQueryParams comes from the owning client, not the current scope. Flagged because that rule is in the review rules file.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
Reviewed by Cursor Bugbot for commit 1aa2891. Configure here.
size-limit report 📦
|


follow up to #25262
This applies
dataCollection.urlQueryParamsto the URLs in the fetch, XHR and navigation breadcrumbs and to theui.element.urlattribute ofelementTimingIntegration. These still sent sensitive query values such as?jwt=...to Sentry.Sentry events
Before (11.6.0),
jwt=sensitive-jwt-valuein the breadcrumbs: https://sentry-sdks.sentry.io/issues/7787761489/events/2bfc6630501c4314bf84b884a4afb1e9/After (this PR),
jwt=[Filtered]: https://sentry-sdks.sentry.io/issues/7787761463/events/6ae067a147b84e6eb33553ae7ce217c7/