|
|
Additional information: I tried the same progress with my android mobile. Here a new contact could be created in zimbra. Thus I assume the problem to be located in TB/SOGo connector.
Christian |
|
gregor
2016-01-01 17:01
reporter
~0009220
Last edited: 2016-01-03 18:08
|
I have here the same problem + it's possible to create contacts from an android device synchronized with carddav-sync.
Client:
sogo connector 31.0.2
thunderbird 38.5.0-1
arch linux 4.2.5-1-ARCH 0000001
Server:
zimbra 8.6.0_GA_1153.RHEL6_64_20141215151155 RHEL6_64
CentOS release 6.7 (Final)
error console:
Upload failure uploading card: https://<servername>/dav/<username>/<contact folder>/C6E65447-5060-0001-EE10-1690DE85B1C0.vcf.
HTTP Status Code:409
- card properties:
0 prop: [xpconnect wrapped nsIProperty]; name: DisplayName; value: 0000test
1 prop: [xpconnect wrapped nsIProperty]; name: RecordKey; value: 344
2 prop: [xpconnect wrapped nsIProperty]; name: PreferMailFormat; value: 0
3 prop: [xpconnect wrapped nsIProperty]; name: DbRowID; value: 159
4 prop: [xpconnect wrapped nsIProperty]; name: groupDavVersionPrev; value: -1
5 prop: [xpconnect wrapped nsIProperty]; name: PopularityIndex; value: 0
6 prop: [xpconnect wrapped nsIProperty]; name: PhotoType; value: generic
7 prop: [xpconnect wrapped nsIProperty]; name: LastModifiedDate; value: 1451666906
8 prop: [xpconnect wrapped nsIProperty]; name: FirstName; value: 0000test
9 prop: [xpconnect wrapped nsIProperty]; name: groupDavKey; value: C6E65447-5060-0001-EE10-1690DE85B1C0.vcf
10 prop: [xpconnect wrapped nsIProperty]; name: CardUID; value: C6E65447-5060-0001-EE10-1690DE85B1C0.vcf
11 prop: [xpconnect wrapped nsIProperty]; name: groupDavVersion; value: -1
12 prop: [xpconnect wrapped nsIProperty]; name: PreferDisplayName; value: 1
-
done
UPDATE: Now I switched to ownCloud as Carddav-Server and there I get after some contacts a error 412 and sometimes the error console filled up with "too much recursion" |
|
|
|
I believe this is related to this:
http://community.zimbra.com/collaboration/f/1897/t/1136671
"Those clients are not specifying an If-None-Match header and Zimbra is requiring that header - although it is a SHOULD rather than a MUST in RFC6352 the specification for CardDAV." |
|
|
|
Well, it was related. Attaching a patch to fix the issue. |
|
Napkin
2016-02-01 15:22
reporter
|
0003-Make-uploading-of-contacts-work-with-Zimbra.patch (1,654 bytes)
From 07df4c16a75f2aa912cc263d9a72ecce0ea48d86 Mon Sep 17 00:00:00 2001
From: "Marc H. Thoben" <mthoben@mpipz.mpg.de>
Date: Mon, 1 Feb 2016 15:50:22 +0100
Subject: [PATCH 3/3] Make uploading of contacts work with Zimbra.
* According to bug reports (#84246) Zimbra <8.7beta1 required
* "If-None-Match" header when posting CardDAV requests.
---
chrome/content/inverse-library/sogoWebDAV.js | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/chrome/content/inverse-library/sogoWebDAV.js b/chrome/content/inverse-library/sogoWebDAV.js
index d5725ac..5a1bf64 100644
--- a/chrome/content/inverse-library/sogoWebDAV.js
+++ b/chrome/content/inverse-library/sogoWebDAV.js
@@ -342,14 +342,16 @@ sogoWebDAV.prototype = {
dump("NOTICE: uploading modified vcard without etag\n");
this._sendHTTPRequest(operation,
parameters.data,
- { "content-type": parameters.contentType });
+ { "content-type": parameters.contentType,
+ "If-None-Match": "*" });
}
}
}
else {
this._sendHTTPRequest(operation,
parameters.data,
- { "content-type": parameters.contentType });
+ { "content-type": parameters.contentType,
+ "If-None-Match": "*" });
}
}
else if (operation == "PROPFIND") {
--
2.6.2
|
|
keynet
2016-04-10 10:57
reporter
~0009954
Last edited: 2016-04-10 18:52
|
I can confirm the issue with Zimbra 8.6 (current) and that the fix works
|
|
|
|
For me it's not working.
On which version did you apply the patch? I tried 31.0.2 and 31.0.3
Can you please add the full xpi, thanks. |
|
|
|
31.0.3 has the proposed patch. |
|
|
|
With the clean 31.0.3 version it doesn't work on my side. Maybe some other problems. I will recreate the damaged contacts manually |
|
|
|
Suspending for unless - waiting for new evidences. |
|
