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

Talk about client half-close #431

Merged
merged 9 commits into from Aug 14, 2020
Merged

Talk about client half-close #431

merged 9 commits into from Aug 14, 2020

Conversation

mnot
Copy link
Member

@mnot mnot commented Aug 6, 2020

Fixes #22.

draft-ietf-httpbis-messaging-latest.xml Outdated Show resolved Hide resolved
draft-ietf-httpbis-messaging-latest.xml Outdated Show resolved Hide resolved
mnot and others added 3 commits August 11, 2020 13:00
Co-authored-by: Roy T. Fielding <fielding@gbiv.com>
... and separate paragraphs
@mnot mnot requested a review from royfielding August 11, 2020 03:12
@irvingreid
Copy link

Historical note: HTTP 1.0 arguably specified the "abort request if the client half-closes" behaviour, see the last paragraph of https://www.rfc-editor.org/rfc/rfc1945#section-1.3, two pages down, just above https://www.rfc-editor.org/rfc/rfc1945#section-1.4. This behaviour was implemented by several widely used HTTP servers; I worked on a firewall product at the time, and we had to take great care to make sure we handled TCP half-close correctly...

The "arguably' is that RFC 1945 says "the closing of the connection by either or both parties", but sending a FIN doesn't really "close" the connection - that requires either a RST or both ends ACK-ing the other end's FIN.

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

Successfully merging this pull request may close these issues.

Clarify rules around half-closed TCP connections
5 participants