Enforcing a Server-side Deadline

[bsnuggs1]

I noticed in the documentation that there's a way to set a deadline per connection, but it seems like this has to be initiated from the client side.

Is there a way to force a server-side deadline?

[antoniomika]

@bsnuggs1 what's the use case here? We have idle deadlines in place (see here). Is what you need different?

Specifically:

      --idle-connection                                         Enable connection idle timeouts for reads and writes (default true)
      --idle-connection-timeout duration                        Duration to wait for activity before closing a connection for all reads and writes (default 5s)

[bsnuggs1]

Thanks for following up! I first thought idle-connection would be sufficient as well, but I think I have users that will tunnel applications that use websockets and forget to close the connection when they're done.

I haven't verified it yet, but I assumed this would cause reads/writes even when the tunneled application isn't being "actively" used.