Thanks Bernd for the quick reply. I start the web application and use the URL https://www.careerbuilder.com/Share/LogIn.aspx?. This handshake is fine and the server redirects to another URL https://accounts.careerbuilder.com/Share/LogIn.aspx? and when the handshake happens with this host it fails.
When it fails and I retry several times to see it the handshake succeeds. But it was failing always. After say 15 or 20 min, when I retry the same URL, the handshake succeeds and the application proceeds fine. I shall try to get the wireshark trace tomorrow. Regards Vasu On 20 October 2016 at 03:28, <e...@zusammenkunft.net> wrote: > Hello, > > Can you publish that trace so we can have a look at it. Your textual > description is not clear to me. > > Does it fail every time for the same host, or what does „many times“ mean? > > Gruss > Bernd > -- > http://bernd.eckenfels.net > > > Von: Vasudevan Comandur > Gesendet: Mittwoch, 19. Oktober 2016 23:48 > An: HttpClient User Discussion > Betreff: Clarification needed on SSL protocol > > Hi, > > I am using HTMLUnit stack to connect to some websites. It was an HTTPS > session. Some times the SSL handshake goes through successfully but > many > times the SSL handshake fails. > > When I looked into the wireshark trace, what I found is the following: > > Client - Client Hello on SSLv2 protocol with the list of cipher suites > sent. > > Server - Alert code 0 on TLSV1 protocol > > Client - Alert Code 10 on TLSV1 protocol > > The app gets SSL peer not authenticated exception. > > Is there any reason why it fails?. But I did not see this behaviour > with the real > browser (FF)?. How this can be fixed from the client side? > > THanks in advance for the reply. > > Regards > Vasu > >
