davical/testing/tests/regression-suite/2250-RRULE-expansion-PUT.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

48 lines
1.4 KiB
Plaintext

HTTP/1.1 201 Created
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
ETag: "460f45321d679808addb06c1370d4253"
Content-Length: 0
Content-Type: text/plain; charset="utf-8"
SQL Query 1 Result:
CalDAV Data: >BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//davical.org//NONSGML AWL Calendar//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/New_York
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Repeating event
UID:complex-rrule-issue268
DTSTART;TZID=America/New_York:20220720T091000
RRULE:FREQ=MINUTELY;INTERVAL=15;BYDAY=MO,TU,WE,TH,FR;BYHOUR=9,10
,11,12,13,14,15,16
END:VEVENT
END:VCALENDAR
<
caldav_type: >VEVENT<
class: >NULL<
dav_etag: >460f45321d679808addb06c1370d4253<
description: >NULL<
dtend: >2022-07-20 09:10:00<
dtstart: >2022-07-20 09:10:00<
due: >NULL<
location: >NULL<
logged_user: >10<
percent_complete: >NULL<
priority: >NULL<
rrule: >FREQ=MINUTELY;INTERVAL=15;BYDAY=MO,TU,WE,TH,FR;BYHOUR=9,10,11,12,13,14,15,16<
status: >NULL<
summary: >Repeating event<
transp: >NULL<
tz_id: >America/New_York<
uid: >complex-rrule-issue268<
url: >NULL<
user_no: >10<
~Duration: >00:00:00<