Also, if you ignore the name checking of the cert (i.e. just blindly accept it... dangerous to do with anything important) I've found that you'll often either get a connection timeout or -5 error from the plugin. Not sure if this is specifically related to SAN support (i.e. is there additional negotiation that needs to be done?) or if there are some newer https features that need to be added...

On Aug 23, 2017 2:37 AM, "Marcel Taeumel" <marcel.taeumel@hpi.de> wrote:

Note that due to incomplete or missing SAN support on some platforms, using alternative names can still raise a SqueakSSLCertificateError:

WebClient httpGet: 'https://google.com'

Best,
Marcel

Am 22.08.2017 22:14:38 schrieb Ron Teitelbaum <ron@usmedrec.com>:

SqueakSSL

WebClient httpGet: 'https://www.google.com'

Ron

On Tue, Aug 22, 2017 at 3:09 PM, Eliot Miranda <eliot.miranda@gmail.com> wrote:
Hi All,

what are people using for https support?

_,,,^..^,,,_
best, Eliot