diff --git a/testing/tests/regression-suite/501-iCal-PROPFIND.result b/testing/tests/regression-suite/501-iCal-PROPFIND.result
new file mode 100644
index 00000000..c0a19c0d
--- /dev/null
+++ b/testing/tests/regression-suite/501-iCal-PROPFIND.result
@@ -0,0 +1,34 @@
+HTTP/1.1 207 Multi-Status
+Date: Dow, 01 Jan 2000 00:00:00 GMT
+DAV: 1, 2, access-control, calendar-access
+ETag: "840f74443f877d300a546ff6a4e8dd1c"
+Content-Length: 743
+Content-Type: text/xml; charset="utf-8"
+
+
+
+
+ /caldav.php/user1/
+
+
+ User 1
+
+ /caldav.php/user1/
+
+
+ /caldav.php/user1/
+
+
+ HTTP/1.1 200 OK
+
+
+
+
+
+
+
+
+ HTTP/1.1 404 Not Found
+
+
+
diff --git a/testing/tests/regression-suite/501-iCal-PROPFIND.test b/testing/tests/regression-suite/501-iCal-PROPFIND.test
new file mode 100644
index 00000000..761dadea
--- /dev/null
+++ b/testing/tests/regression-suite/501-iCal-PROPFIND.test
@@ -0,0 +1,31 @@
+#
+# Testing with a process similar to iCal 3 (preferably 3.0.1+)
+#
+TYPE=PROPFIND
+URL=http://mycaldav/caldav.php/user1/
+HEAD
+
+HEADER=User-Agent: DAVKit/2.0 (10.5; wrbt) iCal 3.0
+HEADER=Content-Type: text/xml
+HEADER=Depth: 0
+
+#
+# This query from iCal 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
+
+
+
+
+
+
+
+
+
+
+
+
+ENDDATA