After some Rewriting Mess and a quick&dirty script to give the correct output I
managed to give Apple Addressbook the right top-level-root automatically.
Apple Addressbook _ONLY_ issues a
PROPFIND /
on port 8843 on the server given by the user. There are NO OTHER controls.
I managed my apache to give the right top-level-property-url for the given user
(after Apache LDAP auth and %{LA-U:REMOTE_USER} with [PT] ).
Result (sogo.log, after Addressbook found out the toplevel directory for DAV):
127.0.0.1 - - [29/Jul/2010:12:42:16 GMT] "PROPFIND /SOGo/dav/pascal/ HTTP/1.1"
207 374/167 0.023 - - 0
127.0.0.1 - - [29/Jul/2010:12:42:16 GMT] "PROPFIND
/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/ HTTP/1.1" 207 331/232 0.033
- - 0
Jul 29 12:43:03 sogod: SOGo watchdog [1799]: [obj-dav-dispatch] did not find a
method to server the REPORT
127.0.0.1 - - [29/Jul/2010:12:43:03 GMT] "REPORT
/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/ HTTP/1.1" 501 201/150 0.024
- - 0
[obj-dav-dispatch] did not find a method to server the REPORT
Is the show stopper here:
Apple Addressbook issues:
REPORT /SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/ HTTP/1.1
Host: bafoussam.rz.uni-konstanz.de:8843
User-Agent: Carnet%20d%E2%80%99adresses/870 CFNetwork/454.9.7 Darwin/10.4.0
(i386) (iMac5%2C1)
Content-Type: text/xml; charset=utf-8
Accept: */*
Accept-Language: fr-fr
Accept-Encoding: gzip, deflate
Authorization: XXXXXXXXXXXXX
x-webobjects-server-port: 8843
x-webobjects-server-name: bafoussam.rz.uni-konstanz.de:8843
x-webobjects-server-url: https://bafoussam.rz.uni-konstanz.de:8843
x-webobjects-server-protocol: HTTP/1.0
x-webobjects-remote-host: 127.0.0.1
X-Forwarded-For: 134.34.1.113
X-Forwarded-Host: bafoussam.rz.uni-konstanz.de:8843
X-Forwarded-Server: bafoussam.rz.uni-konstanz.de
Connection: close
Content-Length: 572
<?xml version="1.0" encoding="utf-8" ?><C:addressbook-multiget xmlns:D="DAV:"
xmlns:C="urn:ietf:params:xml:ns:carddav"><D:prop><D:getetag/><C:address-data/></D:prop><D:href>/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/55CC-4C4DD400-5-93E2980.vcf</D:href><D:href>/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/55CC-4C4DD400-7-93E2980.vcf</D:href><D:href>/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/55D3-4C4DD400-1B-6AE9230.vcf</D:href><D:href>/SOGo/dav/pascal/Contacts/55D3-4C4DD400-19-6AE9230/55D3-4C4DD480-1D-6AE9230.vcf</D:href></C:addressbook-multiget>
Result:
HTTP/1.0 501 Request failed
content-length: 201
content-type: text/html; charset="iso-8859-1"
<?xml version="1.0" encoding="ISO-8859-1"?>
<html xmlns="http://www.w3.org/1999/xhtml";>
<body><h3>An error occurred during object publishing</h3><p>did not find the
specified REPORT</p></body>
</html>
SOGo told Apple Addressbook about the existence of these four Entries (.vcf).
Addressbook issues a REPORT command afterwards for these four "cards",
resulting in a 501 Request failed error from Sogo.
What's going on there?
--
Pascal Gienger
University of Konstanz, IT Services Department ("Rechenzentrum")
Electronic Communications and Web Services
Building V, Room V404, Phone +49 7531 88 5048, Fax +49 7531 88 3739
--
users@sogo.nu
https://inverse.ca/sogo/lists
