Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client disconnects after 240s if server timeout is set to 300s #184

Open
neben opened this issue Jan 22, 2025 · 0 comments
Open

Client disconnects after 240s if server timeout is set to 300s #184

neben opened this issue Jan 22, 2025 · 0 comments

Comments

@neben
Copy link

neben commented Jan 22, 2025

I've set the server timeout to 300 seconds (--timeout 300), but now I'm seeing the clients always disconnect after 240s. This looks like the initial client timeout. IIUC the server should update the client timeout to twice the server timeout. Is this timeout info sent with the server keep-alive packet? And is the keep-alive packet sent timeout seconds after connection establishment? This then would explain that if I set the server timeout (300s) to a value higher than the initial timeout (240s), the client times out before ever receiving the timeout update.

If that is the case, wouldn't it make sense to transmit the server timeout value to the client upon connection establishment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant