Skip to content

docs(migration): Fix httpHeaders shape in dataCollection baseline - #23169

Open
andreiborza wants to merge 1 commit into
developfrom
ab/migration-datacollection-http-headers
Open

docs(migration): Fix httpHeaders shape in dataCollection baseline#23169
andreiborza wants to merge 1 commit into
developfrom
ab/migration-datacollection-http-headers

Conversation

@andreiborza

@andreiborza andreiborza commented Aug 7, 2026

Copy link
Copy Markdown
Member

What

Fix the httpHeaders entry in the "keep the v10 default behavior" example, in both MIGRATION.md and docs/migration/v11-end-state.md.

- httpHeaders: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
+ httpHeaders: {
+   request: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
+   response: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
+ },

Closes: #23168

Why

httpHeaders takes { request, response }, not a bare CollectBehavior. A top-level deny matches neither key, so resolveDataCollectionOptions fell back to the true default for both and collected every header, the opposite of what the example promises. TypeScript users hit a compile error, but JavaScript configs failed silently while appearing to opt out.

`httpHeaders` takes `{ request, response }`, not a bare `CollectBehavior`.
The baseline example passed `{ deny: [...] }` directly, which matches
neither key, so both resolved to their `true` default and collected every
header instead of applying the denylist.

Apply the same fix to `docs/migration/v11-end-state.md`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MIGRATION.md: v10 to v11 dataCollection example silently collects all HTTP headers

2 participants