quic, no local idle connection timeout, ngtcp2 keep-alive #17057
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bagder
approved these changes
Apr 16, 2025
tatsuhiro-t
reviewed
Apr 16, 2025
Do not set a transport parameter idle timeout, meaning we have no such thing from our side. The remote setting then applies. In ngtcp2, set its "keep-alive" timer to prevent a possible remote idle timeout to tear down the connection while we have active transfers on that connection.
bagder
approved these changes
Apr 18, 2025
nbaws
pushed a commit
to nbaws/curl
that referenced
this pull request
Apr 26, 2025
Do not set a transport parameter idle timeout, meaning we have no such thing from our side. The remote setting then applies. In ngtcp2, set its "keep-alive" timer to prevent a possible remote idle timeout to tear down the connection while we have active transfers on that connection. Closes curl#17057
nbaws
pushed a commit
to nbaws/curl
that referenced
this pull request
Apr 26, 2025
Do not set a transport parameter idle timeout, meaning we have no such thing from our side. The remote setting then applies. In ngtcp2, set its "keep-alive" timer to prevent a possible remote idle timeout to tear down the connection while we have active transfers on that connection. Closes curl#17057
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not set a transport parameter idle timeout, meaning we have no such thing from our side. The remote setting then applies.
In ngtcp2, set its "keep-alive" timer to prevent a possible remote idle timeout to tear down the connection while we have active transfers on that connection.