Implement reconnect when proxy terminates connections without cutting of tunneled connections
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Our proxy terminates websockets after 48 hours. ( --keepalive just helped a "bit", so that the proxy won't close after 180 seconds )
The inner (tunneled) connections will also get terminated. It would be nice, to have a reconnection option within a window of a few seconds.
This way the inner (tunneled) connections would not suffer a termination.
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, tests, or entry points. Start by tracing how the websocket termination affects the tunneled connections, then determine the reconnection behavior and timing window needed to preserve them. Done means the requested reconnection option is implemented and verified for proxy-terminated connections.
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
- Needs clarification
- Newbie friendliness
- 25/100