Hi David,
Thanks for your reply.
The wireshark trace saved as a file and was attached to the previous
mail. The trace file should be opened using wireshark app.
What I had noticed was that when execute a ping command on
accounts.careerbuilder.com the IP address after DNS resolution is
having one value.
When I execute ping from one of my clients network, it was throwing a
different IP address. Also, my observation was that
with the IP address that was in the WireShark trace the handshake fails
on SSL. However, with another IP address the handshake
through SSL works.
What is the reason for this behaviour?.
I appreciate your reply and thanks in advance.
Regards
Vasu
On 22 October 2016 at 00:42, David Motes <davidmo...@gmail.com> wrote:
> I do not see any trace attached.
>
> That is an old sdk. It might be it is trying to connect with SSL and the
> server only supports TLS. Might want to try a newer sdk.
>
> Or your intermediate certs are not right, There should be some previous
> posts discussing that issue.
>
> On Fri, Oct 21, 2016 at 10:23 AM, Vasudevan Comandur <vcoman...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Attached is the Wireshark log file wherein the application got SSL
> peer
> > not authenticated error but the trace shows that SSL handshake
> > did not succeed.
> >
> > Is it possible to tell why the Alert message came from the server?
> >
> > We are using JDK 1.6.
> >
> > Appreciate your clarification on this and thanking you in advance.
> >
> > Regards
> > Vasu
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org
> > For additional commands, e-mail: httpclient-users-h...@hc.apache.org
> >
>
