Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Jerome Louvel
Hi Alex, This is an issue with Restlet internal HTTP connector (for dev purpose only at this point). Could you try to add and register the org.restlet.ext.net.jar connector? Best regards, Jerome -- http://restlet.org http://twitter.com/#!/jlouvel 2013/5/6 Alex alexdim...@yahoo.gr New

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Alex
Hello Jerome, thanks a lot for responding. If gaving the org.restlet.ext.net.jar on your classpath is enough, then I've already done what you're suggesting. As I stated on my first post, I'm not using the internal http connector, but instead the apache httpclient. In any case, I've even

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Jerome Louvel
Alex; You to put the connector in the first postion doing this: Engine.getInstance().getRegisteredClients().add(*0, *new org.restlet.ext.net .HttpClientHelper(null)); Best regards, Jerome 2013/5/6 Alex alexdim...@yahoo.gr Hello Jerome, thanks a lot for responding. If gaving the

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Alex
-connect-with-HTTPS-SSL-recoverable-error-1001-tp7578771p7578782.html To unsubscribe from Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001, click here. NAML -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/Android-client

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Jerome Louvel
.html To unsubscribe from Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001, click here. NAMLhttp://restlet-discuss.1400322.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Alex
Ok, I found the root cause of the problem. It had nothing to do with Restlet or my code. It was all a matter of installing correctly the intermediate certificates on AWS. The certificate chain of my CA consists of 4 certificate files, and AWS needs this chain in a very specific order (signing

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-06 Thread Jerome Louvel
Thanks Alex for the follow-up, I'm sure it will help other users. Cheers, Jerome 2013/5/6 Alex alexdim...@yahoo.gr Ok, I found the root cause of the problem. It had nothing to do with Restlet or my code. It was all a matter of installing correctly the intermediate certificates on AWS. The

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-05 Thread Alex
Ok, it is as I was suspecting. The problem is that the certificate (having a CNAME = www.mydomain.com, but being loaded from https://mywebservice.elasticbeanstalk.com) seems to the Android client as invalid, thus it doesn't even send the GET/POST request to the server. I realized this when I send

Re: Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-03 Thread Alex
Hello again, I've also tried the Android project with 2.1.2 libraries, but now I'm stuck on the exception /*java.lang.RuntimeException: Unable to create SSLContext*/ caused by /*java.security.NoSuchAlgorithmException: TrustManagerFactory SunX509 implementation not found*/. The only reference I

Android client - Restlet 2.0.15 - cannot connect with HTTPS/SSL - recoverable error 1001

2013-05-02 Thread Alex
Hi all, I have written an Android web service client using the Restlet framework for Android (2.0.15), and I've also written the web service backend as well (again with Restlet 2.0.15 JEE) which has been uploaded on AWS Elastic Beanstalk (so the client calls would be in the form of