nik/davical
1
0
Fork 0
mirror of https://gitlab.com/davical-project/davical.git synced 2026-05-30 03:24:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Apparently it is OK to use REPORT on normal collections.

Browse Source
This commit is contained in:
Andrew McMillan 2006-12-10 22:39:27 +13:00
parent e776477715
commit 1be3e5d320
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
inc/caldav-OPTIONS.php
View File

@ -54,21 +54,19 @@ if ( !$exists ) {
if ( isset($c->override_allowed_methods) )
$allowed = $c->override_allowed_methods;
else {
$allowed = "OPTIONS, GET, HEAD, PUT, DELETE, PROPFIND, MKCOL, MKCALENDAR, LOCK, UNLOCK";
if ( $is_calendar ) $allowed .= ", REPORT";
$allowed = "OPTIONS, GET, HEAD, PUT, DELETE, PROPFIND, MKCOL, MKCALENDAR, LOCK, UNLOCK, REPORT";
}
header( "Allow: $allowed");
/**
* From reading the "Scheduling Extensions to CalDAV" draft I don't think that we will
* be doing this any time soon. The current spec is at:
* be doing 'calendar-schedule' any time soon. The current spec is at:
* http://www.ietf.org/internet-drafts/draft-desruisseaux-caldav-sched-02.txt
*
* access-control is rfc3744, so we will say we do it, but I doubt if we do it
* in all it's glory really.
* in all (or even much of) it's glory really.
*/
$dav = "1, 2, access-control";
if ( $is_calendar ) $dav .= ", calendar-access";
$dav = "1, 2, access-control, calendar-access";
header( "Allow: $allowed");
header( "DAV: $dav");
// header( "DAV: 1, 2, access-control, calendar-access, calendar-schedule");