Skip to content

sdk: Forward custom headers to tunnel requests and relays - #685

Open
Connor Peet (connor4312) wants to merge 1 commit into
microsoft:mainfrom
connor4312:vscode-tunnel-request-headers
Open

Connor Peet (connor4312) wants to merge 1 commit into
microsoft:mainfrom
connor4312:vscode-tunnel-request-headers

Conversation

@connor4312

Copy link
Copy Markdown
Member

Summary

  • Add static and per-request header providers to the Rust management client, forwarding their values to management HTTP requests and relay WebSocket handshakes.
  • Forward TypeScript management-client headers to Node.js relay WebSocket connections, with tests for management request IDs and relay propagation.
  • Document that browser WebSocket APIs cannot attach custom handshake headers; browser management requests continue to support them.

This enables VS Code to send its tunnel session and operation IDs and a new request ID for each service request. Consumer dependency updates will follow the SDK release.

Validation

  • cargo test --manifest-path rs/Cargo.toml --no-default-features --features connections (20 passed)
  • TypeScript tsc --build ts/tsconfig.json
  • Focused Mocha suites for additional management headers, per-request IDs, and relay forwarding (3 passed)

Allow Rust management clients to configure static and per-request headers for management calls and relay handshakes. Forward TypeScript management headers to Node.js relay connections so VS Code can correlate each service request. Browser WebSocket handshakes cannot set custom headers.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.

2 participants