Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Implement Well-Known URIs (RFC 5785)

rfc2822 developer last edited by

Used as an alternative to current-user princial service discovery, this would maybe allow to use OwnCloud CalDAV+CardDAV in one account.

(See .well-known links in http://doc.owncloud.org/server/6.0/admin_manual/installation/installation_source.html)
Reply Quote 0
1 Reply Last reply
rfc2822 developer last edited by

This will require to follow redirections (see #83), but only for configuration (not while syncing).
Reply Quote 0
1 Reply Last reply
A
AutoImport-yvesf last edited by

this is maybe a bit off-topic. I solved this two-accounts-needed problem with a custom plugin that combines carddav/caldav. https://github.com/yvesf/owncloud-apps-dav
Reply Quote 0
1 Reply Last reply
A
AutoImport-rsertelon last edited by

@rfc2822 Do you plan to add autodiscovery support via SRV DNS records as stated in RFC 6764?
Reply Quote 0
1 Reply Last reply
devvv4ever admin last edited by

Yes, it is planned that we implement this! But other things have to be done first, so it may take a while.
Reply Quote 0
1 Reply Last reply
A
AutoImport-rsertelon last edited by

No problem I was asking, because if the answer is yes (and it is), I will configure it on my server
Reply Quote 0
1 Reply Last reply
rfc2822 developer last edited by

Please follow up at #352.
Reply Quote 0
1 Reply Last reply

enhancement 199

7
Posts

1258
Views

Log in to reply

Tweets by DAVx5App

Similar topics

Support Collection Synchronization for WebDAV
Ideas, future talk, development • enhancement • • rfc2822

3

0
Votes

3
Posts

1738
Views

We’re testing Collection Sync support for contacts with the latest DAVdroid development version. While testing, we have encountered some problems when limiting results (which would by very useful especially for DAVdroid) with certain servers/services: https://github.com/nextcloud/server/issues/9339 fruux (reported over support form on 29 Apr 2018) iCloud: works, but ignores limit (should send 507) (will be updated) So collection syncs seems to be working with all tested services which support it, but we can’t and won’t use limiting results for now.
P

.well-known url not checked w/o SRV RR
DAVx⁵ • • Philipp

7

0
Votes

7
Posts

1785
Views

J

@rfc2822 said: RFC 6764 Client “Bootstrapping” Procedures: If an SRV record is not found, the client will need to prompt the user to enter the FQDN and port number information directly or use some other heuristic, for example, using the extracted “domain” as the FQDN and default HTTPS or HTTP port numbers. In this situation, clients MUST first attempt an HTTP connection with TLS. But this is part of step 2. Determination of service FQDN and port number. But we are at step 3. Determination of initial “context path”. and there it is: When an initial “context path” has not been determined from a TXT record, the initial “context path” is taken to be “/.well-known/caldav” (for CalDAV) or “/.well-known/carddav” (for CardDAV). Which is the situation we have: No SRV and no TXT record. I find it overly strict to read this in a way, that a vaild SRV record is a precondition to trying to use wll-known paths.
A

Default phone number for contact reset after sync
DAVx⁵ • enhancement • • AutoImport-trevor87

3

0
Votes

3
Posts

928
Views

Done in 0.5.6 (commit 4f1488ece5)

1 / 1