Hey there,
after playing around with Davical some months ago, I'm now back on its implementation. The reading part was easy, updating events is also working, but I cannot get adding new events to work out.
I'm sending a PUT with this body:
BEGIN:VCALENDAR
PRODID:-//davical.org//NONSGML AWL Calendar//EN
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
SUMMARY:PUTtest
CREATED:20101109T090607Z
DTSTART;TZID=Europe/Berlin:20101116T121000
DTEND;TZID=Europe/Berlin:20101116T131000
END:VEVENT
END:VCALENDAR
The answer from the server then is
HTTP/1.1 201 Created
Date: Tue, 09 Nov 2010 09:06:07 GMT
Server: Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny9 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g
X-Powered-By: PHP/5.2.6-1+lenny9
DAV: 1, 2, access-control, calendar-access, calendar-schedule, extended-mkcol, calendar-proxy, bind, calendar-auto-schedule
X-DAViCal-Version: DAViCal/0.9.9; DB/1.2.8
Content-Length: 0
Connection: close
Content-Type: text/plain; charset="utf-8"
... but it's not sending an etag. I checked the log and compared it with adding a even through Sunbird.
On the communication side the only real difference is that SB is sending a VTIMEZONE with the event which I'm omitting.
The log is showing that my event got added to caldav_data with an etag. Then he's done and sends the 201. With SB the data is also added to caldav_item and he's including the etag into the response.
What am I doing wrong? Why the difference? Is VTIMEZONE required? And why is the RFC 4791 sometimes pretty useless?
I couldn't track the problem down yet, but I'll add some more debug logging to Davical now.
Best regards
Matthias
after playing around with Davical some months ago, I'm now back on its implementation. The reading part was easy, updating events is also working, but I cannot get adding new events to work out.
I'm sending a PUT with this body:
BEGIN:VCALENDAR
PRODID:-//davical.org//NONSGML AWL Calendar//EN
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
SUMMARY:PUTtest
CREATED:20101109T090607Z
DTSTART;TZID=Europe/Berlin:20101116T121000
DTEND;TZID=Europe/Berlin:20101116T131000
END:VEVENT
END:VCALENDAR
The answer from the server then is
HTTP/1.1 201 Created
Date: Tue, 09 Nov 2010 09:06:07 GMT
Server: Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny9 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g
X-Powered-By: PHP/5.2.6-1+lenny9
DAV: 1, 2, access-control, calendar-access, calendar-schedule, extended-mkcol, calendar-proxy, bind, calendar-auto-schedule
X-DAViCal-Version: DAViCal/0.9.9; DB/1.2.8
Content-Length: 0
Connection: close
Content-Type: text/plain; charset="utf-8"
... but it's not sending an etag. I checked the log and compared it with adding a even through Sunbird.
On the communication side the only real difference is that SB is sending a VTIMEZONE with the event which I'm omitting.
The log is showing that my event got added to caldav_data with an etag. Then he's done and sends the 201. With SB the data is also added to caldav_item and he's including the etag into the response.
What am I doing wrong? Why the difference? Is VTIMEZONE required? And why is the RFC 4791 sometimes pretty useless?
I couldn't track the problem down yet, but I'll add some more debug logging to Davical now.
Best regards
Matthias