Error 403 from Google Calendar? Upgrade to the new Google Calendar support. See here for details. close
Welcome, Guest
Please Login or Register.    Lost Password?

Modifying an existing CalDav item fails
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: Modifying an existing CalDav item fails
#20413
Modifying an existing CalDav item fails 10 Months, 3 Weeks ago  
I have a calendarserver running on my NAS, which works fine with other clients. With Rainlendar Pro 2.12 however, modifying an existing calendar item fails: the server responds with an error 403 (Forbidden).
Looking at the network traffic with Wireshark reveals that the server responds with error description "Can't parse calendar data".
The calendar entry that Rainlendar tried to write with the PUT command (data taken from the wireshark capture):
BEGIN:VCALENDAR
PRODID:-//Rainlendar/CalDAVPlugin V1.2//EN
VERSION:2.0
BEGIN:VEVENT
DTSTAMP:20140105T205944Z
TRANSP:OPAQUE
X-RAINLENDAR-CALDAV-HREF:
/calendars/__uids__/g_ruud/calendar/cb016032-d11f-084c-bb6a-5182a7731890.i
cs
X-RAINLENDAR-CALDAV-ETAG:\"0f530704004b0253ac6bd99ecd151f06\"
UID:{cb016032-d11f-084c-bb6a-5182a7731890}
SUMMARY:Test
CLASS:PRIVATE
LAST-MODIFIED:20140105T210326Z
DTSTART:20140108T210000Z
DTEND:20140108T210700Z
END:VEVENT
END:VCALENDAR

The X-RAINLENDAR-CALDAV-HREF line contains 2 sequences of <CR><LF><SPACE> !
I suppose that is the reason the server rejects this modified calendar item.

Note that creating a new calendar item with rainlendar works fine (these items do not contain the X-RAINLENDAR-CALDAV-HREF line).

Attached the Wireshark capture file
File Attachment:
File Name: Rainlendar_capture.zip
File Size: 1785
RuudP
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2014/01/05 15:30 By RuudP.
The administrator has disabled public write access.
 
#20421
Re: Modifying an existing CalDav item fails 10 Months, 3 Weeks ago  
The space after the newline is used to fold long lines in the iCalendar files. It probably is not what's causing the issue but you can try this by entering a long summary for a new event and it should be split in multiple lines too the same way.

What could be the reason for the parsing failure is the escaped quotes in the X-RAINLENDAR-CALDAV-ETAG. There is an old bug reported about it: trac.calendarserver.org/ticket/419

Check what the value of the INVALID_ESCAPE_SEQUENCES is in the server's parser.py file. If it is PARSER_RAISE try changing it to PARSER_FIX, restart the server and see if that helps.
Rainy
Moderator
Posts: 6059
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#20427
Re: Modifying an existing CalDav item fails 10 Months, 3 Weeks ago  
Thanks for the quick and to-the-point response.
I located the parser.py file, made the change you suggested and restarted the calendarserver.
That solves the problem!
The question now is: is this a calendarserver bug or a libical bug in Rainlendar?

Regards,
Ruud
RuudP
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
get the latest posts directly to your desktop