@Bluebird As I see it, these two statements are two sides of the same coin: Orbot should implement a “real” HTTP proxy so that http:// URLs work, or applications should implement “HTTP CONNECT” instead of using the normal HTTP protocol for proxied http:// URLs. So at the moment, unfortunately only https:// links will work with Orbot + DAVx5, because Orbot doesn’t provide a real HTTP proxy, DAVx5 doesn’t use “HTTP CONNECT”, but the normal HTTP protocol for proxied http:// URLs (while https:// URLs always imply HTTP CONNECT). I’ll add that to the DAVx5 FAQ when I have more time.

@rfc2822, yes, actually, if you please, while I was trying to make my hidden service working, I found, that it may be convenient in such cases to save entry even when it is not valid for now, just marking it as out of sync or something like this. Thus it will be possible to edit such entries later without filling credentials again, you know. Just an idea.