Skip to content

Configurable timeout for tailscale transport protocol #124

Description

@FIGBERT

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions