theLizard wrote:OK, the libs are loading, no longer getting "Cannot Load Library" error but getting Socket Error 10060 - Connection Timed Out
Should I be doing something with the SSLIOHandler properties or HTTP properties
Indy's defaults are
usually sufficient for most cases. But not always.
When I use the latest version of Indy to connect to "http://www.pvoutput.org", using all of Indy's defaults (other than HandleRedirects, which I set to true), TIdHTTP follows the redirect to "https://www.pvoutput.org", and then the HTTPS server immediately closes the TCP connection gracefully as soon as it receives Indy's SSL/TLS handshake hello. TIdSSLIOHandlerSocketOpenSSL throws an OpenSSL exception accordingly, not a timeout error (specifically, it throws an error that says "encountered EOF that violated the protocol", which is normal for an unexpected disconnect during the SSL/TLS handshake process).
Maybe in your case, the server is not closing the connection gracefully, or your OS is not detecting it gracefully. Use a packet sniffer, like Wireshark, to verify. If the connection is not closed gracefully, that might be causing the timeout error (TIdSSLIOHandlerSocketOpenSSL does enable socket timeouts on Windows Vista+).
The same test works fine in web browsers. The difference being that TIdSSLIOHandlerSocketOpenSSL enables only TLS 1.0 by default, but modern web browsers also enable TLS 1.1 and 1.2 as well. When I enable TLS 1.1 in TIdSSLIOHandlerSocketOpenSSL, TIdHTTP is able to connect to the HTTPS URL and retrieve its HTML normally.
So clearly, the HTTPS server in question does not like Indy's use of TLS 1.0 and wants TLS 1.1+ instead.