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

[9.8-9] SHOULD: Servers SHOULD be prepared to receive an incomplete close from the client, since the client can ofte... #231

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

Comments

@saviorand
Copy link
Collaborator

RFC 9112 Requirement

Section: 9.8-9
Keyword: SHOULD

Servers SHOULD be prepared to receive an incomplete close from the client, since the client can often locate the end of server data.¶

Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.8-9

@saviorand saviorand added HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement labels Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
Projects
Status: No status
Development

No branches or pull requests

1 participant