mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-05-18 01:31:21 +00:00
This allows us to have more complex test files where an action is taken, then we test something, then another action is taken, etc. Changes to test files are required so that URL is defined after all the required settings are set. Changes to the result files are either whitespace changes due to above logic changes, or printing out a SQL Result header before each result. I figured it was useful.
30 lines
962 B
Plaintext
30 lines
962 B
Plaintext
HTTP/1.1 207 Multi-Status
|
|
Date: Dow, 01 Jan 2000 00:00:00 GMT
|
|
DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
|
|
DAV: extended-mkcol, bind, addressbook, calendar-auto-schedule, calendar-proxy
|
|
Content-Length: 452
|
|
Content-Type: text/xml; charset="utf-8"
|
|
|
|
<?xml version="1.0" encoding="utf-8" ?>
|
|
<multistatus xmlns="DAV:">
|
|
<response>
|
|
<href>/caldav.php/user1/home/</href>
|
|
<responsedescription>Some properties were not able to be changed.</responsedescription>
|
|
<propstat>
|
|
<prop>
|
|
<resourcetype/>
|
|
</prop>
|
|
<status>HTTP/1.1 409 Conflict</status>
|
|
<responsedescription>A collection may not be both a calendar and an addressbook.</responsedescription>
|
|
</propstat>
|
|
</response>
|
|
</multistatus>
|
|
|
|
SQL Query 1 Result:
|
|
changed_last_5m: >1<
|
|
dav_displayname: >User One's addressbook<
|
|
is_addressbook: >1<
|
|
is_calendar: >0<
|
|
resourcetypes: ><collection xmlns="DAV:"/><addressbook xmlns="urn:ietf:params:xml:ns:carddav"/><
|
|
|