thanks all.
yes i think the problem is with the server certificate authentication.
the app is connecting to my own server https://www.myserver.com/url..
looks like the easiest work-around is to skip the authentication.
On May 22, 10:23 pm, DanH wrote:
> Assuming the server is legitimate, yo
It's also quite possible the certificate chain is a bit iffy.
You can check this quite easily by surfing to the URL with the *built-
in browser* in your Android phone. If the certificate works there but
*not* in your app (i assume you are using the Apache HttpClient?) its
most often your chain tha
Assuming the server is legitimate, you basically see this problem
because the certificate presented by the HTTPS server doesn't have a
certificate chain that can be verified against one of the root
certificates on the phone. It may be possible to download and install
a new (additional) root author
Contact a server with a valid certificate?
So far, it's not sounding like a problem with your client (Android) app.
Nick
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.
4 matches
Mail list logo
