I can sympathize with how my question must sound ridiculous. But I have tried many combinations of parameters to OpenSSL and curl with no luck. It's looking a

I can sympathize with how my question must sound ridiculous. But I have tried many combinations of parameters to OpenSSL and curl with no luck. It's looking at this point that the problem is due to an MTU below 1500: http://askubuntu.com/questions/189752/cant-connect-to-certain-https-sites/189829#189829 http://askubuntu.com/questions/189752/cant-connect-to-certai... But if that's the case, that's a serious problem with their OpenSSL implementation, because there is no way to control how packets are split once they are on the internet. All SSL should require is a single socket connection that can send and receive bytes, regardless of underlying protocol. My frustration with this is that we shouldn't be seeing these types of issues this late in game with something as fundamental as SSL. This bug never should have made it into a stable release, and if it did, it should have been fixed immediately.