On Aug 14, 2012, at 8:49 PM, Michael McMahon
wrote:
> Xuelei,
>
> We have no particular requirement on HostnameVerifier. So,
> if I understood you correctly, HostnameVerifier is redundant in new APIs
> and it is possible to control hostname verification through the SSLParameters
> class
> (and
On 14/08/12 13:11, Alan Bateman wrote:
On 14/08/2012 04:11, Frank Ding wrote:
On 8/7/2012 1:46 PM, Frank Ding wrote:
:
Could anybody take a look at my patch below and make comment?
http://cr.openjdk.java.net/~youdwei/ojdk-533/webrev.00/
Thanks & Best regards,
Frank
Hi all,
Is there anybod
On 08/08/12 21:35, Chris Hegarty wrote:
Great suggestion Anthony,
This is something that comes up from time to time. With the clear
distinction between java.net.HttpURLConnection and
javax.net.ssl.HttpsURLConnection API's then it was a little difficult
to do in the existing API, but there is
On 14/08/2012 04:11, Frank Ding wrote:
On 8/7/2012 1:46 PM, Frank Ding wrote:
:
Could anybody take a look at my patch below and make comment?
http://cr.openjdk.java.net/~youdwei/ojdk-533/webrev.00/
Thanks & Best regards,
Frank
Hi all,
Is there anybody who is interested in the patch and who
Xuelei,
We have no particular requirement on HostnameVerifier. So,
if I understood you correctly, HostnameVerifier is redundant in new APIs
and it is possible to control hostname verification through the
SSLParameters class
(and an X509ExtendedTrustManager).
So, we can drop HostnameVerifier fr
Hi,
(apologies for sending this again)
We have just published a draft of a proposed new Http client API [1] for
JDK 8.
This message has been cc'd to jdk8-dev so that as many people as possible
know about it, but the discussion will be on the net-dev list
(net-dev@openjdk.java.net).
So, folks
