We have to connect with our application (written in Java 8) to some very old server using HTTPS. Being Java 8, our client supports TLSv1.2, TLSv1.1, TLSv1 and SSLv3. Of course, it prefers to use TLSv1.2, as it's the newest protocol.
The server (Oracle-HTTP-Server 18.104.22.168), however, only supports TLSv1 and SSLx. Additionally, it has a very limited selection of supported cipher suites, but there is still one suite in common that we can use with TLSv1: SSL_RSA_WITH_3DES_EDE_CBC_SHA (a.k.a. TLS_RSA_WITH_3DES_EDE_CBC_SHA).
However, straightforward connection fails with the server terminating handshake. Debug output we get (on the client side) looks like this:
main, WRITE: TLSv1.2 Handshake, length = 265 main, READ: TLSv1 Alert, length = 2 main, RECV TLSv1.2 ALERT: fatal, close_notify main, called closeSocket() main, handling exception: javax.net.ssl.SSLException: Received fatal alert: close_notify
To me, it looks like the server doesn't even try to fall back to TLSv1: as soon as the client declares TLSv1.2 as preferred, the server bails out.
In comparison, when we explicitly disable TLSv1.2 and TLSv1.1 in our client, thus making TLSv1 the preferred option, handshake succeeds.
We also tried to connect to another legacy server that doesn't know about TLSv1.2 and TLSv1.1, but here connection works as expected: even though the client says it prefers TLSv1.2, they agree with the server to use TLSv1, as the best common protocol:
main, WRITE: TLSv1.2 Handshake, length = 269 main, READ: TLSv1 Handshake, length = 85 ...
Question: is it the server's duty to choose out of the list of TLS/SSL protocols the client supports? Can I say to the server maintainers that it is the server that misbehaves, not our client?