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.5-3] MAY: A client, server, or proxy MAY close the transport connection at any time. For example, a client mig... #212

Open
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.5-3
Keyword: MAY

A client, server, or proxy MAY close the transport connection at any time. For example, a client might have started to send a new request at the same time that the server has decided to close the "idle" connection. From the server's point of view, the connection is being closed while it was idle, but from the client's point of view, a request is in progress.¶

Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.5-3

@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
Labels
HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements
Projects
Status: No status
Development

No branches or pull requests

1 participant