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.7-2] MUST: The HTTP client also acts as the TLS client. It initiates a connection to the server on the appropri... #226

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

Comments

@saviorand
Copy link
Collaborator

RFC 9112 Requirement

Section: 9.7-2
Keyword: MUST

The HTTP client also acts as the TLS client. It initiates a connection to the server on the appropriate port and sends the TLS ClientHello to begin the TLS handshake. When the TLS handshake has finished, the client may then initiate the first HTTP request. All HTTP data MUST be sent as TLS "application data" but is otherwise treated like a normal connection for HTTP (including potential reuse as a persistent connection).¶

Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.7-2

@saviorand saviorand added HTTP/1.1 HTTP/1.1 specification MUST Mandatory 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 MUST Mandatory requirement RFC9112 RFC 9112 requirements
Projects
Status: No status
Development

No branches or pull requests

1 participant