-
Notifications
You must be signed in to change notification settings - Fork 88
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
SNI from a server #175
Comments
It does seem sensible to acknowledge receipt of the extension, regardless of whether it is actually used to determine a corresponding certificate or security policy. That way, clients are less likely to spuriously abort the connection if they choose to insist on the extension ACK. So I would view a PR that implements the sending of an empty extension favourably, if such functionality is not yet present. |
OK. I will implement it. |
…#175) RFC 6066: A server that receives a client hello containing the "server_name" extension MAY use the information contained in the extension to guide its selection of an appropriate certificate to return to the client, and/or other aspects of security policy. In this event, the server SHALL include an extension of type "server_name" in the (extended) server hello. The "extension_data" field of this extension SHALL be empty.
Fixed with #178. |
RFC6066 says:
But I cannot find the code to send an empty SNI from a server to a client. Is this intentional? Or is it just missing?
The text was updated successfully, but these errors were encountered: