-
Notifications
You must be signed in to change notification settings - Fork 221
Validate upstream JSON-RPC responses in transparent proxy #5288
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
Open
bishnubista
wants to merge
7
commits into
stacklok:main
Choose a base branch
from
bishnubista:fix/validate-upstream-jsonrpc-responses
base: main
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.
+703
−4
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a7badd9
Validate upstream JSON-RPC responses in transparent proxy
bishnubista 4909903
Merge branch 'main' into fix/validate-upstream-jsonrpc-responses
amirejaz cac0d28
Merge remote-tracking branch 'origin/main' into fix/validate-upstream…
bishnubista f70c56c
Tighten upstream JSON-RPC response validation
bishnubista c0a8b6c
fix(proxy): reuse MCP response validation helper
bishnubista 01fc505
Merge remote-tracking branch 'origin/main' into fix/validate-upstream…
bishnubista 7dbb1f7
Merge branch 'main' into fix/validate-upstream-jsonrpc-responses
bishnubista 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
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.
Scoping to non-SSE makes sense for now — SSE validation would need a fundamentally different approach. By the time
ProcessResponseruns on an SSE response, the200 OKandContent-Type: text/event-streamheaders are already committed downstream, so there is no way to rewrite to 502 for a malformed mid-stream event. A proper fix would need a per-event streaming interceptor inside the SSE processor that can either synthesize an error event or close the stream — a meaningfully larger scope than this PR.Worth opening a follow-up issue to track it explicitly, so it is clear the gap is deferred rather than forgotten.