-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(cloudflare): Migrate to dataCollection
#21237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
chargome
wants to merge
1
commit into
develop
Choose a base branch
from
cg/cloudflare-datacollection
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+42
−11
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auth and session cookies now captured in Sentry events by default after removing explicit cookie exclusion
Removing the explicit
{ include: { cookies: false } }guard fromrequestDataIntegration()causes all HTTP cookies — including session tokens, auth tokens, and CSRF cookies — to be captured in Sentry error events by default, because the new defaultdataCollection.cookiesvalue ({ deny: PII_HEADER_SNIPPETS }) evaluates totruein theinclude.cookiescheck and the event path inextractNormalizedRequestDataperforms no further deny-list filtering.Evidence
requestDataIntegration()(no options) callsresolveIncludeAndDataCollection(client)inpackages/core/src/integrations/requestdata.ts.dataCollectionorsendDefaultPiiset,client.getDataCollectionOptions()returnscookies: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] }— patterns for IP headers, not cookie names.include.cookies = dataCollection.cookies !== falseevaluates totruebecause{ deny: [...] } !== false.extractNormalizedRequestDatathen unconditionally executesrequestData.cookies = parseCookie(headers.cookie)wheninclude.cookiesistrue, adding all cookies toevent.request.cookieswith no deny-list filtering.requestDataIntegration({ include: { cookies: false } })short-circuited this path entirely; theSENSITIVE_COOKIE_NAME_SNIPPETSfiltering only applies in the span/httpHeadersToSpanAttributespath, not in the event processing path.Identified by Warden security-review · EBZ-JZ3