From: Gustaf N. <ne...@wu...> - 2017-12-07 11:13:20
|
Dear Michael, the only sane solution is to add client SNI support to nsssl. I will try to look into what this means in detail over the weekend. all the best -g Am 12/6/17 um 8:35 PM schrieb Steigman, Michael: > Hi, > > I am updating an application that uses TLS (with -servername option) and Tcllib's rest package to post data to an HTTPS URI. I’d like to use ns_http but based on my tinkering, it does not appear that ns_http handles SNI. I tried plain old ns_http and also ns_http with TLS, e.g. > > http::register https 443 ::tls::socket > tls::init -tls1 true -ssl2 false -ssl3 false -servername my-host.com > set h [ns_http queue -method POST -headers $queryHeaders -body "test" https://my-host.com/] > ns_http wait -status S -result R $h > > I get a 503 in either case. Am I missing something? > > TIA, > > Michael > > > > The information in this e-mail is intended only for the person to whom it is > addressed. If you believe this e-mail was sent to you in error and the e-mail > contains patient information, please contact the Partners Compliance HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to you in error > but does not contain patient information, please contact the sender and properly > dispose of the e-mail. > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel -- Univ.Prof. Dr. Gustaf Neumann WU Vienna Institute of Information Systems and New Media Welthandelsplatz 1, A-1020 Vienna, Austria |