Hi, I have been playing with DAViCal recently using iCal on Leopard for the client. I am using version 0.95 and have one issue with it. A quirk in iCal sends a PROPFIND followed by a PROPPATCH request to the server root (/) upon every calendar addition and deletion. It doesn't seem to matter where DAViCal is hosted, the requests always go to /. The calendar is created/deleted successfully, but sending a PROPFIND/PROPPATCH to / triggers a 403 error and iCal pops up a dialog box to report it.
I discovered that the PROPFIND/PROPPATCH requests were being sent to caldav.php and it was throwing a 403 error to the PROPPATCH request (in caldav-PROPPATCH.php in response to a disallowed write property). I'm not sure how iCal's seemingly unnecessary PROPPATCH request should be handled. I'm not sure when this error catch would become a necessity, but I found that replacing the 403 error with a success code solved the problem for the moment.
If anyone has any suggestions on how something like this could be properly handled in the code I'd be happy to test it out. In the meantime, I have a fully functioning DAViCal server and am easily syncing my calendars between my laptop and desktop. Thanks for the great software!
by GlowingApple (not verified) at 2008-05-27 17:20
PROPFIND/PROPPATCH to / with iCal
Hi, I have been playing with DAViCal recently using iCal on Leopard for the client. I am using version 0.95 and have one issue with it. A quirk in iCal sends a PROPFIND followed by a PROPPATCH request to the server root (/) upon every calendar addition and deletion. It doesn't seem to matter where DAViCal is hosted, the requests always go to /. The calendar is created/deleted successfully, but sending a PROPFIND/PROPPATCH to / triggers a 403 error and iCal pops up a dialog box to report it.
I discovered that the PROPFIND/PROPPATCH requests were being sent to caldav.php and it was throwing a 403 error to the PROPPATCH request (in caldav-PROPPATCH.php in response to a disallowed write property). I'm not sure how iCal's seemingly unnecessary PROPPATCH request should be handled. I'm not sure when this error catch would become a necessity, but I found that replacing the 403 error with a success code solved the problem for the moment.
If anyone has any suggestions on how something like this could be properly handled in the code I'd be happy to test it out. In the meantime, I have a fully functioning DAViCal server and am easily syncing my calendars between my laptop and desktop. Thanks for the great software!