mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-05-24 02:24:39 +00:00
7c47658bee
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.
32 lines
1021 B
Plaintext
32 lines
1021 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: 529
|
|
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 403 Forbidden</status>
|
|
<responsedescription>DAV::resourcetype may only be set to a new value, it may not be removed.</responsedescription>
|
|
<error>
|
|
<cannot-modify-protected-property/>
|
|
</error>
|
|
</propstat>
|
|
</response>
|
|
</multistatus>
|
|
|
|
SQL Query 1 Result:
|
|
changed_last_60se: >1<
|
|
dav_displayname: >User One's Transparent Calendar<
|
|
is_calendar: >1<
|
|
resourcetypes: ><collection xmlns="DAV:"/><calendar xmlns="urn:ietf:params:xml:ns:caldav"/><
|
|
|