I've used /sockopen -e on many domains on port 443 which is typical https:// and have no issues with data and communicating with a http server. Are you saying that this isn't SSL, but TLS? What's a webserver address where communicating with it with /sockopen -e would fail? I can't find an example of a https:// server that the data is garbage or connection refused using /sockopen -e, and those POODLE and DROWN attacks were addressed and fixed with new OpenSSL versions so that should be by the wayside if using a newer OpenSSL Lib.
