> Regards the OP problem: thinking about this further, what's the point
> of using HTTPS if you're going to ignore certificate errors ?
I can think of a few reasons. If the root CA is trusted by the user, but the root cert is not installed on the device, the encryption is still valid, but an error would occur. The same holds true if the cert is expired, or if it is a self signed cert. Certainly it increases the risk, but if the user is comfortable with those risks, it's still better to use https instead of http.
I love this app, and I was trying to configure an HTTP GET action using SSL and noticed that it doesn't play too nice with self-signed/untrusted certificates. This is the error I get:"Input/Output error for https://example.com/blah: javax.net.ssl.SSLHandshakeException: java.security.cert. CertPathValidatorException: Trust anchor for certification path not found..."I'm using a self-signed certificate so I wasn't all that surprised to see the error, but was hoping that maybe you could add an option to the HTTP GET (and probably HTTP POST, too) to be able to ignore any certificate errors? I tried adding the certificate to the built-in trusted store in Jelly Bean, but that didn't seem to do anything. Even the browser still threw an error so I'm guessing the trust store only works for WiFi/VPN certs.I'm using the latest Beta so I'm open to test out any changes if you consider incorporating this.