Hi Yann.
I am using exactly the same configuration as you: Latest eGroupware, Thunderbird and Galaxy S.
Funambol client v10 for Android: Not working for me either. I use the older v9 of Funambol for contact synchronisation which works just fine.
4myPal worked ok too.
Event sync:
AnDal did not work for me either. Same error message, no answer from the developers yet.
CalDAV-Sync: I tried it with 3 eGroupware servers. One server worked out of the box. The second server worked half-way, the app passed the configuration step, but then the synchronisation failed. The solution was that my web site hoster had some mod_security rule which prevented the CalDav request from succeeding. I got the following information from my hoster:
Error report:
…
Match of “rx (^application/x-www-form-urlencoded|^multipart/form-data;|^text/xml).*$” against “REQUEST_HEADERS:Content-Type” required.
…
Rules:
…
Only accept request encodings we know how to handle
we exclude GET requests from this because some (automated)
clients supply “text/html” as Content-Type
SecRule REQUEST_METHOD “!^(get|head|options|post|put|propfind)$” chain,deny,log,id:90001,status:406
SecRule HTTP_Content-Type “!(^application/x-www-form-urlencoded|^multipart/form-data;|^text/xml).*$”
…
When the hoster removed this mod_security rule, everything worked as expected (except the 2-way sync, but this is in alpha testing so I do not expect it to work perfectly…)
The third server does not work yet. I have the same behaviour as you, not being able to pass the configuration step. I have been in contact with the developer of CalDAV-Client, Marten Gajda (German speaking), who is very nice and willing to solve the problem. His last answer to me was the following, stating a missing “D:” namespace in the server reply:
"ich glaube ich habe eben das eigentliche Problem gefunden. Wie du in der Antwort von deinem Server siehst, fehlt bei dem “href” Tag der Namespace “D:”. Daher wird das Tag von meiner App ignoriert und die Adresse zu dem Principal Home nicht gefunden.
Am 11.08.2011 21:42, schrieb Daniel Tamm:
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D=“DAV:”>
<D:response xmlns:ns0=“urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/”>
<D:href>/egroupware/groupdav.php/</D:href>
<D:propstat>
<D:prop>
<D:current-user-principal>http://www.kvarnhjulet.se/egroupware/groupdav.php/principals/users/daniel.tamm/</D:current-user-principal>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
Hat da jemand evtl. was an der Konfiguration gedreht, oder kannst du ein Update auf eine neuere Version machen?"
I have not yet followed up this, but I am not aware of any modification of my eGroupware configuration. If you have the possibility to make a tcpdump on your server, send it to Marten Gajda, maybe this helps both of us since we get the same erraneous behaviour.
