davical/testing/tests/regression-suite/2601-POST-freebusy-confidential.result
Andrew Ruthven 7c47658bee Make the curl and SQL requests when we see them
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.
2024-04-01 22:57:10 +13:00

44 lines
1.4 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: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:20230416T000000Z
DTEND:20230421T000000Z
FREEBUSY:20230416T210000Z/20230416T212500Z
FREEBUSY:20230418T230000Z/20230418T232500Z
FREEBUSY:20230419T210000Z/20230419T212500Z
FREEBUSY:20230420T210000Z/20230420T212500Z
UID:c5bd82ea-cd89-4f58-8d31-336f47e44f98
ORGANIZER:mailto:user4@example.net
ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL:
mailto:user1@example.net
END:VFREEBUSY
END:VCALENDAR
</C:calendar-data>
</C:response>
</C:schedule-response>
SQL Query 1 Result:
class: >CONFIDENTIAL<
dav_name: >/user1/291-test-fb-rr-changes/409f61c7243c61c382a0795fd97249618e39543c.ics<
finish: >20230418T232500Z<
rrule: >NULL<
start: >20230418T230000Z<
class: >CONFIDENTIAL<
dav_name: >/user1/291-test-fb-rr-changes/d126ea19c4f19eed5dbac8d8a1578b022fa5cec9.ics<
finish: >20230416T212500Z<
rrule: >FREQ=DAILY;COUNT=5<
start: >20230416T210000Z<