Comment 2 for bug 1035558

I've done some further testing. First I recompiled OpenSSL with SSLv2 support. I received the same error when connecting to api.samurai.feefighters.com. I went back to the command line and tested more options to try and narrow down the problem. Here are the results:

openssl s_client -connect api.samurai.feefighters.com:443 -ssl2 Error (expected as remote server has disabled SSLv2)
openssl s_client -connect api.samurai.feefighters.com:443 -ssl3 Works
openssl s_client -connect api.samurai.feefighters.com:443 -tls1 Works
openssl s_client -connect api.samurai.feefighters.com:443 -tls1_1 Error
openssl s_client -connect api.samurai.feefighters.com:443 -tls1_2 Error

openssl s_client -connect api.samurai.feefighters.com:443 -no_ssl2 Error
openssl s_client -connect api.samurai.feefighters.com:443 -no_ssl3 Error
openssl s_client -connect api.samurai.feefighters.com:443 -no_tls1 Error
openssl s_client -connect api.samurai.feefighters.com:443 -no_tls1_1 Works
openssl s_client -connect api.samurai.feefighters.com:443 -no_tls1_2 Error

The second to last line demonstrates to me that the remote server is configured to prefer TLSv1.1, and somewhere there is a bug which is causing the connection to fail when using TLSv1.1. There is also an error when using TLSv1.2 but I am uncertain if the remote server supports TLSv1.2