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.

Sign up for GitHub

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

Jump to bottom

ConnectTimeout should also cancel the handshake/initialization procedure when the server stopped responding #3

Open
MarcusWichelmann opened this issue Sep 30, 2020 · 0 comments
Open

ConnectTimeout should also cancel the handshake/initialization procedure when the server stopped responding #3

MarcusWichelmann opened this issue Sep 30, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@MarcusWichelmann
Copy link
Owner

When the TCP socket is open, but the server is not responding (wrong port or server process is paused/broken) the ConnectTimeout should still have an effect.
Currently, the server is waiting forever for a response.

Maybe use the builtin ReceiveTimeout and disable it as soon as the connection is initialized?

Add a separate ProtocolTimeout/HandshakeTimeout/whatever property to the connect parameters?
@MarcusWichelmann MarcusWichelmann added the enhancement New feature or request label Sep 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MarcusWichelmann