After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653103 - Cannot modify WebDAV contact
Cannot modify WebDAV contact
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Contacts
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-06-21 12:54 UTC by Milan Crha
Modified: 2014-03-11 16:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-06-21 12:54:20 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=714719

I can list, search, create and delete contacts on my WebDAV address book
(hosted on a Zimbra 7 server) just fine, but when I try to edit a contact and
modify anything, I get an error:

> Error modifying contact
> Cannot modify contact: Modify contact failed with HTTP status: 409 (Conflict)

Version-Release number of selected component (if applicable):
3.0.2-2.fc15

How reproducible:
Always

Steps to Reproduce:
1. Setup a WebDAV address book that is hosted on a Zimbra server
2. Add a new contact and save it
3. Open the contact and try to change something

Actual results:
I get the error described above

Expected results:
It should accept the change
Comment 1 Milan Crha 2011-06-21 12:54:35 UTC
Confirming, I can reproduce it too.
Comment 2 Milan Crha 2011-06-21 14:11:25 UTC
This seems to me like a bug on the Zimbra server, though the same done with CalDAV works as expected. What I tried:
I run e-addressbook-factory with WEBDAV_DEBUG=all and I see that the PUT request is done on a correct path, with the correct etag in an "If-Match" header, but the zimbra server responses with 409. If I change a code to use "If-None-Match: *" instead of the exact ETag, then the modification succeeds as expected.

The problem is that I do not have any other server to test this against, to prove the theory about an issue with Zimbra server itself. I'm also pretty sure that this worked with Zimbra 5.x or 6.x (I do not know exact version).
Comment 3 markus.nilsson 2012-02-02 09:13:52 UTC
I am having the same problem

Using Evolution 3.2.2 from debian squeeze
Zimbra (from a service provider), I beleive they are running Zimbra 7.1.1

I have made a report for this on Zimbra Bugzilla as well
https://bugzilla.zimbra.com/show_bug.cgi?id=69777
Comment 4 Milan Crha 2012-02-03 13:34:15 UTC
(In reply to comment #3)
> I have made a report for this on Zimbra Bugzilla as well
> https://bugzilla.zimbra.com/show_bug.cgi?id=69777

Thanks for it.
Comment 5 Milan Crha 2014-03-11 16:33:15 UTC
I retested this with more recent zimbra server (8.0.6), and recent evolution-data-server (3.11.91), and I can modify contacts on a zimbra server now, thus I'm closing this as such.