R
Hi,
DAVx⁵ checks /dav.php/principals/naman/ for CalDAV/CardDAV:
2019-10-19 02:07:15 2311 [HttpClient] --> OPTIONS https://dav.namandixit.net/dav.php/principals/naman/
2019-10-19 02:07:15 2311 [HttpClient] --> END OPTIONS
2019-10-19 02:07:15 2311 [HttpClient] <-- 204 https://dav.namandixit.net/dav.php/principals/naman/ (67ms)
2019-10-19 02:07:15 2311 [HttpClient] access-control-allow-headers: User-Agent,Authorization,Content-type,Depth,If-match,If-None-Match,Lock-Token,Timeout,Destination,Overwrite,Prefer,X-client,X-Requested-With
2019-10-19 02:07:15 2311 [HttpClient] access-control-allow-methods: GET, POST, OPTIONS, PROPFIND, PROPPATCH, REPORT, PUT, MOVE, DELETE, LOCK, UNLOCK
2019-10-19 02:07:15 2311 [HttpClient] access-control-allow-origin: *
2019-10-19 02:07:15 2311 [HttpClient] access-control-expose-headers: Etag,Preference-Applied
2019-10-19 02:07:15 2311 [HttpClient] access-control-max-age: 1728000
2019-10-19 02:07:15 2311 [HttpClient] content-type: text/plain; charset=utf-8
2019-10-19 02:07:15 2311 [HttpClient] date: Fri, 18 Oct 2019 20:37:15 GMT
2019-10-19 02:07:15 2311 [HttpClient] server: nginx/1.17.3
2019-10-19 02:07:15 2311 [HttpClient] content-length: 0
2019-10-19 02:07:15 2311 [HttpClient] <-- END HTTP (0-byte body)
and expects DAV: calendar-access for CalDAV or DAV: addressbook for CardDAV: https://gitlab.com/bitfireAT/davx5-ose/blob/cd9518c6194752d172d06f2bb12e2ec802419f2a/app/src/main/java/at/bitfire/davdroid/ui/setup/DavResourceFinder.kt#L296
In your case, those headers are not sent for /dav.php/principals/naman/, so DAVx⁵ wont’t detect/use that URL. (Note that your server sends the correct headers for /dav.php/, but that’s not enough.) Normally, Baïkal sends those headers correctly.
Does that help?
