mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-05-01 16:11:20 +00:00
b4bcc6cc25
iPhone devices incorrectly implement DAV:current-user-principal from RFC 5397. They assume that current-user-principal is the href for the resource being queried. The RFC says it should be the current resource. See: https://gitlab.com/davical-project/davical/-/issues/335
51 lines
1.5 KiB
Plaintext
51 lines
1.5 KiB
Plaintext
HTTP/1.1 207 Multi-Status
|
|
Date: Dow, 01 Jan 2000 00:00:00 GMT
|
|
Content-Location: /caldav.php/user1/addresses/
|
|
DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
|
|
DAV: extended-mkcol, bind, addressbook, calendar-auto-schedule, calendar-proxy
|
|
ETag: "3f9506c10fe5b434f966d4c82f026c40"
|
|
Content-Length: 1129
|
|
Content-Type: text/xml; charset="utf-8"
|
|
|
|
<?xml version="1.0" encoding="utf-8" ?>
|
|
<multistatus xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:carddav">
|
|
<response>
|
|
<href>/caldav.php/user1/addresses/</href>
|
|
<propstat>
|
|
<prop>
|
|
<getcontenttype>httpd/unix-directory</getcontenttype>
|
|
<resourcetype>
|
|
<collection/>
|
|
<C:addressbook/>
|
|
</resourcetype>
|
|
<displayname>user1 addresses</displayname>
|
|
<getlastmodified>Sun, 15 Mar 1998 12:00:00 GMT</getlastmodified>
|
|
<creationdate>19570725T120000Z</creationdate>
|
|
<getcontentlanguage/>
|
|
<supportedlock>
|
|
<lockentry>
|
|
<lockscope>
|
|
<exclusive/>
|
|
</lockscope>
|
|
<locktype>
|
|
<write/>
|
|
</locktype>
|
|
</lockentry>
|
|
</supportedlock>
|
|
<owner>
|
|
<href>/caldav.php/user1/</href>
|
|
</owner>
|
|
<current-user-principal>
|
|
<href>/caldav.php/user4/</href>
|
|
</current-user-principal>
|
|
<C:max-resource-size>6550000</C:max-resource-size>
|
|
<C:supported-address-data>
|
|
<C:address-data content-type="text/vcard" version="3.0"/>
|
|
</C:supported-address-data>
|
|
</prop>
|
|
<status>HTTP/1.1 200 OK</status>
|
|
</propstat>
|
|
</response>
|
|
</multistatus>
|
|
|