mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-04-18 14:00:17 +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.
48 lines
1.2 KiB
XML
48 lines
1.2 KiB
XML
<?xml version="1.0" encoding="utf-8" ?>
|
|
<C:schedule-response xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
|
|
<C:response>
|
|
<C:recipient>
|
|
<href>mailto:manager1@example.net</href>
|
|
</C:recipient>
|
|
<C:request-status>2.0;Success</C:request-status>
|
|
<C:calendar-data>BEGIN:VCALENDAR
|
|
PRODID:-//davical.org//NONSGML AWL Calendar//EN
|
|
VERSION:2.0
|
|
CALSCALE:GREGORIAN
|
|
METHOD:REPLY
|
|
BEGIN:VFREEBUSY
|
|
DTSTAMP:yyyymmddThhmmssZ
|
|
DTSTART:20111018T110000Z
|
|
DTEND:20111019T110000Z
|
|
FREEBUSY:20111018T210000Z/20111018T220000Z
|
|
UID:E9F98477-A9C2-43F9-8371-CBA0CBCB0300
|
|
ORGANIZER:mailto:manager1@example.net
|
|
ATTENDEE:mailto:manager1@example.net
|
|
END:VFREEBUSY
|
|
END:VCALENDAR
|
|
</C:calendar-data>
|
|
</C:response>
|
|
<C:response>
|
|
<C:recipient>
|
|
<href>mailto:user1@example.net</href>
|
|
</C:recipient>
|
|
<C:request-status>2.0;Success</C:request-status>
|
|
<C:calendar-data>BEGIN:VCALENDAR
|
|
PRODID:-//davical.org//NONSGML AWL Calendar//EN
|
|
VERSION:2.0
|
|
CALSCALE:GREGORIAN
|
|
METHOD:REPLY
|
|
BEGIN:VFREEBUSY
|
|
DTSTAMP:yyyymmddThhmmssZ
|
|
DTSTART:20111018T110000Z
|
|
DTEND:20111019T110000Z
|
|
UID:E9F98477-A9C2-43F9-8371-CBA0CBCB0300
|
|
ORGANIZER:mailto:manager1@example.net
|
|
ATTENDEE:mailto:user1@example.net
|
|
END:VFREEBUSY
|
|
END:VCALENDAR
|
|
</C:calendar-data>
|
|
</C:response>
|
|
</C:schedule-response>
|
|
|