[Feature request] Fallback to HTTP when web sockets aren't available
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
@jpillora I need to tunnel https/http over an http connection specifically to GAE. Using this project would be ideal, however GAE doesn't yet support web sockets. Is there a way to fall back to HTTP when web sockets aren't available?
I know this isn't nearly as natural, but at least in our firewall environment I can only hit an http endpoint without ws support.
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
The issue names no files or tests. Start by locating the WebSocket transport and HTTP endpoint, then determine how a non-WebSocket path could preserve HTTPS/HTTP tunneling for GAE. Done means the tunnel works through an HTTP-only connection and has coverage for environments without WebSocket support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100