diff --git a/htdocs/caldav.php b/htdocs/caldav.php
index ccecb73f..4d89ba1b 100644
--- a/htdocs/caldav.php
+++ b/htdocs/caldav.php
@@ -14,6 +14,18 @@ require_once("HTTPAuthSession.php");
 $session = new HTTPAuthSession();
 dbg_log_array( "headers", '_SERVER', $_SERVER, true );
 
+/**
+* From reading the "Scheduling Extensions to CalDAV" draft I don't think that we will
+* be doing 'calendar-schedule' any time soon.  The current spec is at:
+*    http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-03.txt
+*
+* access-control is rfc3744, so we will say we do it, but I doubt if we do it
+* in all (or even much of) it's glory really.
+*/
+$dav = "1, 2, access-control, calendar-access";
+header( "DAV: $dav");
+// header( "DAV: 1, 2, access-control, calendar-access, calendar-schedule");
+
 require_once("CalDAVRequest.php");
 $request = new CalDAVRequest();
 
diff --git a/inc/caldav-OPTIONS.php b/inc/caldav-OPTIONS.php
index 33c99232..2f1197ea 100644
--- a/inc/caldav-OPTIONS.php
+++ b/inc/caldav-OPTIONS.php
@@ -58,18 +58,6 @@ else {
 }
 header( "Allow: $allowed");
 
-/**
-* From reading the "Scheduling Extensions to CalDAV" draft I don't think that we will
-* be doing 'calendar-schedule' any time soon.  The current spec is at:
-*    http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-03.txt
-*
-* access-control is rfc3744, so we will say we do it, but I doubt if we do it
-* in all (or even much of) it's glory really.
-*/
-$dav = "1, 2, access-control, calendar-access";
-header( "Allow: $allowed");
-header( "DAV: $dav");
-// header( "DAV: 1, 2, access-control, calendar-access, calendar-schedule");
 
 $request->DoResponse( 200, "" );