Skip to content

Transition into closed state only occurs on READING a close frame. #14

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
Merged
merged 6 commits into from
Jul 1, 2023
Merged

Transition into closed state only occurs on READING a close frame. #14

merged 6 commits into from
Jul 1, 2023

Conversation

ioquatix
Copy link
Member

@ioquatix ioquatix commented Jun 1, 2023 •
edited
Loading

Either peer can send a control frame with data containing a specified
control sequence to begin the closing handshake (detailed in
Section 5.5.1). Upon receiving such a frame, the other peer sends a
Close frame in response, if it hasn't already sent one. Upon
receiving that control frame, the first peer then closes the
connection, safe in the knowledge that no further data is
forthcoming.

@ioquatix ioquatix force-pushed the close-ignore-errors branch from 1e37692 to 0f38199 Compare July 1, 2023 02:52
@ioquatix ioquatix merged commit c730f47 into main Jul 1, 2023
@ioquatix ioquatix deleted the close-ignore-errors branch July 1, 2023 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ioquatix