add proxy cookie leak repro test#3809
Closed
MustafaMulla29 wants to merge 1 commit into
Closed
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
/api/proxyrouteWhy
A standard USB-C connector can fail to load in
tsci devbecause the browser sends its localhost analytics cookie to/api/proxy. The proxy currently forwards that cookie to EasyEDA whenX-Sender-Cookieis empty, and EasyEDA's CloudFront/WAF rejects the request with403 Forbidden.The test reproduces the header leak directly using local CLI and target HTTP servers.
Current result
This draft intentionally contains a failing regression test until the proxy fix is implemented:
Validation
bun run format:check— passesbun test tests/cli/dev/proxy-cookie-isolation.test.ts— fails as expected, proving the synthetic localhost cookie reaches the target