Carddav Syncing with EGroupware fails
Hello,
just got back my Jolla and applied the new update 10. Now I can set up a carddav sync account. I tried multiple settings I found in the forum, yet none worked.
I use a hosted EGroupware 14.2 Installation. My Egroupware installation is below xxx.xxx/egroupware
My Carddav Settings are
auth/method = password
server_address = http://XXX.XXX/egroupware/groupdav.php auth/mechanism = password sync_profile_templates = ["carddav.Contacts"] CredentialsId = 31 carddav.Contacts/profile_id = carddav.Contacts-29 enabled = true
From the journal I get the following errors
[D] RequestGenerator::generateRequest:88 - generateRequest(): "" "http://xxx.xxx/egroupware/groupdav.php" "" "0" "PROPFIND" "<d:propfind xmlns:d="DAV:"><d:prop><d:current-user-principal /></d:prop></d:propfind>"
[D] {anonymous}::debugDumpData:48 - "<?xml version="1.0" encoding="utf-8"?>"
[D] {anonymous}::debugDumpData:48 - "<D:multistatus xmlns:D="DAV:">"
[D] {anonymous}::debugDumpData:48 - " <D:response xmlns:ns0="urn:uuid:c1111010-65b3-11d1-a29f-00aa00c14882/">"
[D] {anonymous}::debugDumpData:48 - " <D:href>/egroupware/groupdav.php/</D:href>"
[D] {anonymous}::debugDumpData:48 - " <D:propstat>"
[D] {anonymous}::debugDumpData:48 - " <D:prop>"
[D] {anonymous}::debugDumpData:48 - " <D:current-user-principal><D:href>/egroupware/groupdav.php/principals/users/xxx/</D:href></D:current-user-principal>"
[D] {anonymous}::debugDumpData:48 - " </D:prop>"
[D] {anonymous}::debugDumpData:48 - " <D:status>HTTP/1.1 200 OK</D:status>"
[D] {anonymous}::debugDumpData:48 - " </D:propstat>"
[D] {anonymous}::debugDumpData:48 - " </D:response>"
[D] {anonymous}::debugDumpData:48 - "</D:multistatus>"
[D] CardDav::fetchAddressbookUrls:341 - void CardDav::fetchAddressbookUrls(const QString&) requesting addressbook urls for user
[D] RequestGenerator::generateRequest:88 - generateRequest(): "" "http://xxx.xxx/egroupware/groupdav.php" "/egroupware/groupdav.php/principals/users/xxx/" "0" "PROPFIND" "<d:propfind xmlns:d="DAV:" xmlns:card="urn:ietf:params:xml:ns:carddav"><d:prop><card:addressbook-home-set /></d:prop></d:propfind>"
[D] {anonymous}::debugDumpData:48 - "<?xml version="1.0" encoding="utf-8"?>"
[D] {anonymous}::debugDumpData:48 - "<D:multistatus xmlns:D="DAV:">"
[D] {anonymous}::debugDumpData:48 - " <D:response xmlns:ns0="urn:uuid:c1111010-65b3-11d1-a29f-00aa00c14882/" xmlns:ns2="urn:ietf:params:xml:ns:carddav">"
[D] {anonymous}::debugDumpData:48 - " <D:href>/egroupware/groupdav.php/</D:href>"
[D] {anonymous}::debugDumpData:48 - " <D:propstat>"
[D] {anonymous}::debugDumpData:48 - " <D:prop>"
[D] {anonymous}::debugDumpData:48 - " </D:prop>"
[D] {anonymous}::debugDumpData:48 - " <D:status>HTTP/1.1 200 OK</D:status>"
[D] {anonymous}::debugDumpData:48 - " </D:propstat>"
[D] {anonymous}::debugDumpData:48 - " <D:propstat>"
[D] {anonymous}::debugDumpData:48 - " <D:prop>"
[D] {anonymous}::debugDumpData:48 - " <ns2:addressbook-home-set/>"
[D] {anonymous}::debugDumpData:48 - " </D:prop>"
[D] {anonymous}::debugDumpData:48 - " <D:status>HTTP/1.1 404 Not Found</D:status>"
[D] {anonymous}::debugDumpData:48 - " </D:propstat>"
[D] {anonymous}::debugDumpData:48 - " </D:response>"
[D] {anonymous}::debugDumpData:48 - "</D:multistatus>"
[W] ReplyParser::parseAddressbookHome:219 - QString ReplyParser::parseAddressbookHome(const QByteArray&) const invalid status response to addressbook home request: "HTTP/1.1 404 Not Found"
[W] CardDav::addressbookUrlsResponse:366 - void CardDav::addressbookUrlsResponse() unable to parse addressbook home from response
[D] Buteo::LogTimer::LogTimer:72 - "void CardDavClient::syncFinished(int, const QString&)" :Entry
[C] CardDavClient::syncFinished:137 - CardDAV sync failed: 401 ""
What happens here? Has anyone an idea?
What about the (web) server side log? What do the "principals" requests look like? Double entries in the URL?
cy8aer ( 2015-01-01 12:47:20 +0200 )editMost likely due to a bug which was fixed recently in the CardDAV sync adapter (see https://github.com/nemomobile/buteo-sync-plugin-carddav/commit/1fe6c4f59d4d7afa3d9bed7e5d03f53677992e68) which could sometimes cause the adressbook home set PROPFIND request to be performed on the wrong URL. If this is the case, it will be fixed in the upcoming update (1.1.4).
Cheers, Chris.
chris.adams ( 2015-04-01 06:39:18 +0200 )edit