mirror of https://github.com/etesync/android
I'm a bit conflicted about this one because even though EteSync is end-to-end encrypted, people should be using TLS. I can't think of a reason why anyone would want to use HTTP over HTTPS, especially given let's encrypt exists and EteSync supports self-signed certs, but I guess it's better to allow it for now, at least until we have a nice error message for it. Fixes #81pull/96/head
parent
1f9e7fa6a6
commit
7d7096cc58
Loading…
Reference in new issue