[turba] CardDAV: Contacts don't show up in eMClient or Thunderbird, but *writing* contacts works

[Jan Schneider]

Please don't top-post.

Zitat von Natanji <natanji at gmail.com>:

> Am 11.12.2013 14:53, schrieb Jan Schneider:
>>
>> Zitat von Natanji <natanji at gmail.com>:
>>
>>> Hi,
>>> quickly want to ask around here before I file a bug report. I'm on Horde
>>> 5.1.3 and trying to access my adress book via CardDAV. This works
>>> perfectly fine on my Android with the "CardDav Sync" app, but it doesn't
>>> work completely in eM Client nor in Thunderbird with Inverse SOGo
>>> Connector.
>>>
>>> By "completely" I mean that I can *write* entries to the adress boook
>>> and they show up on the server just fine. So the authentication and
>>> connection to Horde definitely works. And in the logfiles I can
>>> definitely see that Horde is sending the contact data back. But the
>>> response that Horde generates seems to not be understood by the Client;
>>> perhaps it is not correctly formatted. The problem is also documented
>>> here (with logfiles):
>>> http://forum.emclient.com/emclient/topics/carddav_server_contacts_not_showing_in_em_but_when_we_create_contact_on_em_it_is_getting_synced_on_carddav
>>>
>>>
>>> If this is a problem in SabreDAV, it would be a regression: I have
>>> another server with OwnCloud 5 installed, which uses SabreDAV 1.7.6, and
>>> syncing contacts via CardDAV works perfectly fine there. On Horde 5.1.3
>>> we have SabreDAV 1.8.7 so that's *much* more up to date, and it does not
>>> work there.
>>>
>>> I was not able to find any bug in Horde or SabreDAV that sounds like
>>> this, and I don't even know if it's a bug in the sense that
>>> Horde/SabreDAV go against the CardDAV specification (which the eM Client
>>> developers claim) or if it's a bug in the clients I tested. I just
>>> figured I would try here first since it seems weird that multiple
>>> completely different clients would have the same issue.
>>>
>>> Any input on what to do would be greatly appreciated.
>>>
>>> Cheers,
>>> Natanji
>>
>> This might be caused by a bug in SabreDAV which has already been fixed
>> in Horde's Git.
> Can you link me to the bug report, please - or when it was fixed in
> Horde (revision number, maybe)? I'd like to investigate for myself if
> this is a SabreDAV bug or not, and what the details on it are. Right now
> I feel very much in the dark about everything, and I'd like to know what
> we are dealing with here instead of such a "might". ;-) Especially
> because looking through both Horde and SabreDAV bugtrackers did not give
> me any results on such a problem so far.
>
> Cheers,
> Natanji
>

https://github.com/horde/horde/commit/a47872dd33de46d0346f0a117aaf178f7f81d783
https://github.com/fruux/sabre-dav/issues/374
-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject