The commit put me on this way. My calendar was already named calendar.ics, but was not displayed on DAVDroid discovery. I just renamed my address book to addressbook.vcf. The /.well-known/*/ URL now redirect to the correct locations, but DAVDroid stil do not display the calendars and address book in it’s discovery panel. The debug log appears to be correct on Radicale side (extract below) :
PROPFIND request at /.well-known/carddav received
-> <current-user-principal><href>/nhuillard/addressbook.vcf/</href>
PROPFIND request at /nhuillard/addressbook.vcf/ received
-> <prop>CR:addressbook-home-set<href>/nhuillard/addressbook.vcf/</href>
OPTIONS request at /nhuillard/addressbook.vcf/ received
-> 200 OK
PROPFIND request at /nhuillard/addressbook.vcf/ received
with request containing empty items : <prop><CD:addressbook-description xmlns:CD=“urn:ietf:params:xml:ns:carddav”/><displayname/>
-> response containing the whole address book
Ditto for calendar.ics.
Seeing the empty displayname (before my first post), I tried to tweak it in nhuillard/addressbook.vcf.props, adding ‘{“D:displayname”: “something”, …’ to no avail…
All this is with permissions control switched completely off on the Radicale side ([rights] type = None). With permission control on ([rights] type = owner_only), DAVDroid apparently do not reliably send authentication information, leading to some “Anonymous has NO read access to collection nhuillard/calendar.ics/” (I also have two other calendars, used by Tasks and Memos in Evolution, which may scramble the authentication).
Permission control ON on Radicale also breaks Evolution (which is recognized as “Anonymous”, whatever the login setting on Evolution side).