mirror of
https://gitlab.com/davical-project/davical.git
synced 2026-01-27 00:33:34 +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.
35 lines
947 B
Plaintext
35 lines
947 B
Plaintext
#
|
|
# Testing with a process similar to iPhone 3
|
|
#
|
|
TYPE=PROPFIND
|
|
HEAD
|
|
|
|
AUTH=user1:user1
|
|
|
|
HEADER=User-Agent: DAVKit/4.0 (728.3); iCalendar/1 (34); iPhone/3.0 7A341
|
|
HEADER=Content-Type: text/xml
|
|
HEADER=Depth: 1
|
|
|
|
#
|
|
# This query from the iPhone seems to discover several things. Firstly they
|
|
# get the calendar-home-set URL for this path. Secondly, they ascertain
|
|
# whether the calendar supports scheduling, and finally, whether it
|
|
# handles some Apple-specific extensions.
|
|
#
|
|
BEGINDATA
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
<x0:propfind xmlns:x2="http://calendarserver.org/ns/" xmlns:x0="DAV:" xmlns:x3="http://apple.com/ns/ical/" xmlns:x1="urn:ietf:params:xml:ns:caldav">
|
|
<x0:prop>
|
|
<x0:displayname/>
|
|
<x1:calendar-description/>
|
|
<x2:getctag/>
|
|
<x3:calendar-color/>
|
|
<x1:supported-calendar-component-set/>
|
|
<x0:resourcetype/>
|
|
<x0:current-user-privilege-set/>
|
|
</x0:prop>
|
|
</x0:propfind>
|
|
ENDDATA
|
|
|
|
URL=http://regression.host/caldav.php/user1/
|