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

[9.8-8] MAY: Clients MAY send a closure alert before closing the connection. Clients that do not expect to receiv... #230

Open
saviorand opened this issue Jan 15, 2025 · 0 comments
Open

[9.8-8] MAY: Clients MAY send a closure alert before closing the connection. Clients that do not expect to receiv... #230

saviorand opened this issue Jan 15, 2025 · 0 comments
Labels
HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements

Comments

@saviorand
Copy link
Collaborator

RFC 9112 Requirement

Section: 9.8-8
Keyword: MAY

Clients MAY send a closure alert before closing the connection. Clients that do not expect to receive any more data MAY choose not to wait for the server's closure alert and simply close the connection, thus generating an incomplete close on the server side.¶

Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.8-8
@saviorand saviorand added HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements
Projects
HTTP 1.1 Compliance
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@saviorand