Skip to content

pipeline-manager: filter further forwarded pipeline streaming headers#6682

Open
snkas wants to merge 1 commit into
mainfrom
fix-header-forwarding
Open

pipeline-manager: filter further forwarded pipeline streaming headers#6682
snkas wants to merge 1 commit into
mainfrom
fix-header-forwarding

Conversation

@snkas

@snkas snkas commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

The authorization header has already been handled by the API server, and thus does not need to be included in the headers sent to the pipeline.

The `authorization` header has already been handled by the API server,
and thus does not need to be included in the headers sent to the
pipeline.

Signed-off-by: Simon Kassing <simon.kassing@feldera.com>
@snkas
snkas requested a review from gz July 20, 2026 13:21
@snkas
snkas enabled auto-merge July 20, 2026 13:28

@mythical-fred mythical-fred left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sensible narrow fix. authorization gets validated by the API server before the runner ever calls into streaming_proxy, so forwarding it to the pipeline just leaks the bearer token one hop deeper without adding any check on the receiving side. Filter matches the existing casing-insensitive HeaderName == &str pattern used for connection/accept-encoding, so it correctly catches Authorization too. Comment placement is fine.

Optional (non-blocking): if we're building an allow-list mindset here, cookie and proxy-authorization are the other two "credential-ish" headers a caller could set that the pipeline has no business seeing. Worth considering in a follow-up, but scope for this PR is right.

APPROVE.

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.

2 participants