Lines Matching full:hostname
20 <li><a href="#CommonHostnameProbs">Common Problems with Hostname Verification</a></li>
336 <h2 id="CommonHostnameProbs">Common Problems with Hostname Verification</h2>
346 java.io.IOException: Hostname 'example.com' was not verified
369 server for more than one hostname with HTTP, the web server can tell from the HTTP/1.1 request
370 which target hostname the client is looking for. Unfortunately this is complicated with
375 hostname to the server so the proper certificate can be returned.</p>
385 hostname of your virtual host, but the one returned by the server by default.</p>
392 <p>If you are still sure you want to override hostname verification, here is an example
394 with one that still verifies that the hostname is at least on expected by the app:</p>
397 // Create an HostnameVerifier that hardwires the expected hostname.
398 // Note that is different than the URL's hostname:
402 public boolean verify(String hostname, SSLSession session) {
418 <p>But remember, if you find yourself replacing hostname verification, especially
443 {@link javax.net.ssl.SSLSocket} <strong>does not</strong> perform hostname verification. It is
444 up the your app to do its own hostname verification, preferably by calling {@link
445 javax.net.ssl.HttpsURLConnection#getDefaultHostnameVerifier()} with the expected hostname. Further
462 // Verify that the certicate hostname is for mail.google.com
470 // we have performed hostname verification, so it is safe to proceed.
484 resulting in the certificates for a hostname to be issued to
