davical/testing/tests/regression-suite/2707a-PUT-Event.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

47 lines
1.2 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: "a fine looking etag"
Content-Length: 0
Content-Type: text/plain; charset="utf-8"
SQL Query 1 Result:
A1 CalDAV DATA: >BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//artisanal-handcrafted-ICS.com//NONSGML Artisanal.iCal 1.0//EN
BEGIN:VEVENT
CLASS:PUBLIC
DTSTAMP:20240120T034700Z
DTSTART:30000101T000000Z
DURATION:P1H
SUMMARY:Test date in 30000101
TRANSP:OPAQUE
UID:2707-PUT-Event-30000101
RRULE:FREQ=WEEKLY;COUNT=2
END:VEVENT
END:VCALENDAR
<
caldav_type: >VEVENT<
class: >PUBLIC<
description: >NULL<
dtend: >NULL<
dtstamp: >2024-01-20 03:47:00<
dtstart: >NULL<
due: >NULL<
last_modified: >2024-01-20 03:47:00<
location: >NULL<
logged_user: >10<
percent_complete: >NULL<
priority: >NULL<
rrule: >FREQ=WEEKLY;COUNT=2<
status: >NULL<
summary: >Test date in 30000101<
transp: >OPAQUE<
tz_id: >NULL<
uid: >2707-PUT-Event-30000101<
url: >NULL<
user_no: >10<