This repository has been archived by the owner on Sep 29, 2024. It is now read-only.
Handle server-initiated reset #41
Merged
Conversation
This file contains 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
keeshux
force-pushed
the
handle-server-initiated-reset
branch
from
de5e93f
to
0d97c5d
Compare
Session is stale and not recoverable (lame duck).
keeshux
force-pushed
the
handle-server-initiated-reset
branch
from
0d97c5d
to
b1a79d6
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Renegotiation (aka
SOFT_RESET) is not currently handled when requested by the server. After 60s, the server would mark the session as a "lame duck" and send aHARD_RESET. The connection may then stop working.Fixes for when the server sends a spontaneous:
SOFT_RESET: initiate a renegotiation.HARD_RESET: shut down the session/socket.