tailscale / tailscale/caddy-tailscale
Configurable timeout for `tailscale` transport protocol
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 978
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Description
It could be nice to have a configurable (or at least shorter default) timeout, a-la the existing functionality of the upstream http transport.
I am using this image to proxy (like Funnel) from a somewhat unreliable upstream. When the upstream is online but not accepting connections, I can configure the response using the standard handle_errors block. But when upstream is entirely down, it is significantly delayed in calling that block (to the point where I used to think it was never called). This seems unoptimal.
Happy to help in implementing this, would just need some pointers in the right direction about where to start.
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 locating the tailscale transport implementation and comparing its connection timeout behavior with the upstream http transport linked in the issue. Confirm how an entirely unavailable upstream reaches handle_errors, then define a configurable or shorter timeout and verify that the error handler is invoked within that limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100