-
Notifications
You must be signed in to change notification settings - Fork 138
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
Server boilerplate #176
Comments
Excuse me, it looks like |
Lots of people have done it. I think the main reason is that the server has to provide certificates somehow, and there often isn't one obvious way to do this -- the certificates probably need to be renewed as they expire and a server might need to provide certificates for multiple host names, which have to come from somewhere. There's just more degrees of freedom in a server implementation, so providing a generically useful API isn't quite straightforward and/or quite a bit of work. |
Is there a reason beyond "nobody's done it yet" that TlsAcceptor and TlsStream from the server example aren't published by this library? As it is
hyper-rustls
doesn't directly connect hyper and rustls.Also it looks like the HTTP2 ALPN negotiation is on by default for the client per #95 but not the server (by the example) -- is there a reason for this?
The text was updated successfully, but these errors were encountered: