Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

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

Implement Well-Known URIs (RFC 5785)

DAVx⁵

4

7

1300

Log in to reply

R
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)
1 Reply Last reply
Reply Quote 0
R
rfc2822 developer last edited by

This will require to follow redirections (see #83), but only for configuration (not while syncing).
1 Reply Last reply
Reply Quote 0
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
1 Reply Last reply
Reply Quote 0
A
AutoImport-rsertelon last edited by

@rfc2822 Do you plan to add autodiscovery support via SRV DNS records as stated in RFC 6764?
1 Reply Last reply
Reply Quote 0
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.
One must still have chaos in oneself to be able to give birth to a dancing star. – Friedrich Nietzsche
1 Reply Last reply
Reply Quote 0
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
1 Reply Last reply
Reply Quote 0
R
rfc2822 developer last edited by

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

Tweets by DAVx5App

Similar topics

A

Ignore .well-known paths in some cases
DAVx⁵ • • AutoImport-chaoscommander

10

0
Votes

10
Posts

1614
Views

A

It seems that DavDroid currently issues a .well-known request to the server, and only falls back to the user-given URL. I think it should be the other way around.

Currently:

1.) well-known request to server – if that fails, use user-given URL
2.) PROPFIND requesting current-user-principal to found URL

Proposed to fix this issue:

1.) PROPFIND requesting current-user-principal to user-given URL
2.) If that fails, well-known request to server, then issue PROPFIND against the found URL

This is slower but allows the user to deal with “wrong” well-known setups.

#528 could be fixed “on-the-go” by prepending a check if the user-given URL is a collection.
L

Manage Groups and members on Android
Ideas, future talk, development • enhancement • • lcoalhost

3

0
Votes

3
Posts

1203
Views

L

Aaahh okay, thank you for your reply! 😄
T

Remove alarm for a calendar
Ideas, future talk, development • enhancement • • tobiaskaminsky

1

0
Votes

1
Posts

856
Views

T

Hello,
I have a calendar which is shared by my wife.
She puts a lot of events with alarms/notifications in it.
It would be cool if davdroid allows to enable/disable alarms on each calendar.

I know that this could also be part of the server or even the calendar app on android, but as an user might use different server or apps, davdroid is the one single point which is used for all.

Thank you for your great software!

1 / 1