WASM: support DialOptions.HTTPClient
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.5k
- Forks
- 376
- PR merge metrics
- No merged PRs in 30d
Description
Support configuring a custom http.Client for use in a Wasm deployment.
This would support making websocket connections through something like gvisor netstack.
An example of such an http.Client is here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how DialOptions.HTTPClient is handled for WASM deployments, then compare the custom client pattern in the linked WireGuard netstack example. Done means a caller can configure an http.Client and use it for WebSocket connections in a WASM deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, wasm
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100