- Notifications
You must be signed in to change notification settings - Fork425
[#600] Add TLS SNI hostname to client options#601
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
glynos commentedFeb 16, 2016
@theopolis The CI builds are failing, could you update the PR? Also, could you apply this on the master branch? Unfortunately, master and 0.12-devel have diverged in the last few weeks, so it means some duplication of effort. |
theopolis commentedFeb 16, 2016
I'm going to attempt some E2E testing of the SNI support today. I can also submit a PR against cpp-netlib:master, but I wasn't sure if that code was a candidate for a 0.12 release. It seems there's some significant divergence from the 0.11 build w.r.t ASIO and boost. |
theopolis commentedFeb 17, 2016
You'll most likely choose to merge#602, but for posterity: this implementation of SNI does work. Although not captured in unit tests, a traffic dump shows the TLS |
glynos commentedFeb 19, 2016
LGTM |
[#600] Add TLS SNI hostname to client options
This PR adds a new member and API to
http::client::optionsfor an optional TLS SNI hostname. HTTPS client option callsites may optionally support/provide an SNI hostname:The implementation within
ssl_delegateandsync_sslarrive at an OpenSSL (and equivalent API implementations):SSL_set_tlsext_host_name. See the OpenSSL wiki forTLS SNI details, as well as usage examples.Also, there are various non-thesis related style changes pulled in via
clang-formatand the project's local format file. Please let me know if it is unacceptable to piggy-back these changes and I will try to remove them. Most of my editors auto-format so pulling out the changes isdoable. 🙀 😉