title: Play WS SSL acceptAnyCertificate=true issue
body: <p>We are using Play WS SSL firsttime and <code>play.ws.ssl.loose.acceptAnyCertificate: 'true'</code> config which intends to be for disabling Hostname Verification. </p>
  
  <p>But for some reason I see , it still does the host verification and I see the following warnings. </p>
  
  <pre><code>August 3rd 2017, 15:02:25.084   *** ClientKeyExchange, DH
  August 3rd 2017, 15:02:25.083   *** Certificate chain
  August 3rd 2017, 15:02:25.083   ***
  August 3rd 2017, 15:02:25.083   Warning: no suitable certificate found - continuing without client authentication
  August 3rd 2017, 15:02:25.083   0080: 72 70 72 69 73 65 43 41   30 31                    rpriseCA01
  August 3rd 2017, 15:02:25.083   [read] MD5 and SHA1 hashes:  len = 4
  August 3rd 2017, 15:02:25.083   0000: 0E 00 00 00                                        ....
  August 3rd 2017, 15:02:25.083   &lt;Empty&gt;
  August 3rd 2017, 15:02:25.083   *** ServerHelloDone
  </code></pre>
  
  <p>From my understanding,</p>
  
  <pre><code>play.ws.ssl.loose.acceptAnyCertificate: 'true'  --&gt; Strict validation
  play.ws.ssl.loose.acceptAnyCertificate: 'false' --&gt; Loose Validation
  </code></pre>
  
  <p>When we set the flag to <code>false</code> , it was able to identity server cert from keystore and does cert validation and other checks, also the handshake was happening as expected.</p>
  
  <p>Where as when we set the loose config with flag <code>true</code>, it's NOT able to identify the server cert and throws <code>no suitable certificate found</code> warning and handshake fails.</p>
  
  <p>For me it doesn't make any sense as it was working in the strict case but fails in the loose case which is strange behaviour.</p>
  
  <p>I can say when the flag is set to <code>true</code>, play uses JDK's SSLEngine implementation but some other implementation in case the flag is <code>false</code></p>
  
  <p>Any ideas ?</p>
  
  <p>Thanks</p>
  
  <p>Suresh</p>