Thanks for your report, but it’s a duplicate of #439.
[Enhancement] Auto-Detect CalDAV/CardDAV-Paths for well-known platforms
-
Current behaviour:
I have to enter the full path to my ownCloud-CalDAV: http://owncloud.example.com/remote.php/caldavExpected behaviour:
Big, well-known platforms like ownCloud should be recognized by the app automatically.
If i enter only http://owncloud.example.com/ the app should complete the default path automatically.
Of course an exact path should still be possible, but this behaviour would make it very much more easier (especially for new users) to setup a sync. -
There will be no platform-dependent configuration presets because they are subject to change and there’s no reason to keep such a list up-to-date. However, we plan to implement well-known URIs soon (see #148). Well-known URIs are supported by many providers, platform-independent and easy to set up (for OwnCloud, see here: http://doc.owncloud.org/server/5.0/user_manual/pim/troubleshooting.html). When a service is configured correctly, this would exactly achieve what you want – just enter the host or even the domain (SRV records will be supported, too) and the configuration is done automatically.
-
there’s no reason to keep such a list up-to-date.
Well, the big reason is enhanced usability. There are only a handful of DAV servers and even if they do change the address and don’t let you know, the long address will still work.
-
Question: What says the standard? Why is owncloud not following this standard?
@jancborchardt can in owncloud maybe .htaccess rewrite-engine be used to follow up the standard? -
Well, the big reason is enhanced usability. There are only a handful of DAV servers and even if they do change the address and don’t let you know, the long address will still work.
This would be true if there would be no better methods to detect the DAV paths – but there are
And these will be implemented.can in owncloud maybe .htaccess rewrite-engine be used to follow up the standard?
Indeed, see http://doc.owncloud.org/server/5.0/user_manual/pim/troubleshooting.html
(Actually, it’s not “Troubleshooting”.)