On Sun, 2013-04-14 at 17:07 +0200, Philippe Mouawad wrote: > A note about this: > -Dhttps.protocols=SSLv3 > > fixes issue for Java Implementation. > > So it seems the server only supports SSLv3, attempt to negotiate upwards > from v2 to v3 seems not to be supported by server. > > To fix it for HC family it seems we need to call: > > - socket.setEnabledProtocols(new String[] { "SSLv3" }); > > Is there a better way to fix this ? >
Philippe This is the right fix for the problem. What we can do, though, is to provide a configuration option to simplify the initialization process of newly created SSL sockets. Please raise an enhancement request in JIRA for this issue. Oleg > > Thanks > > Regards > Philippe > > On Sun, Apr 14, 2013 at 3:50 PM, Philippe Mouawad < > philippe.moua...@gmail.com> wrote: > > > Hello , > > > > We had a report recently on JMeter project: > > > > - https://issues.apache.org/bugzilla/show_bug.cgi?id=54759 > > > > > > Investigations didn't help us solve issue that seems to occur on this > > particular website: > > > > https://clui.xstratacoal.com.au > > > > And even with JAVA Pure API. > > > > See the 2 snippet attached to the bug inspired from: > > > > - > > > > http://javaskeleton.blogspot.fr/2010/07/avoiding-peer-not-authenticated-with.html > > - > > > > http://javaskeleton.blogspot.fr/2011/01/avoiding-sunsecurityvalidatorvalidatore.html > > > > > > Any ideas about this ? > > > > Thanks > > > > Regards > > > > Philippe > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org