Move the DAV: header to caldav.php, rather than only sending it for

the OPTIONS request.
This commit is contained in:
Andrew McMillan 2007-10-29 18:14:10 +13:00
parent c0a00fd419
commit ca10fb50c1
2 changed files with 12 additions and 12 deletions

View File

@ -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();

View File

@ -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, "" );