Open madduck opened 6 years ago
In RFC 5545, "3.1. Content Lines" it's written:
Content lines are delimited by a line break, which is a CRLF sequence (CR character followed by LF character).
However, Radicale writes its files using Unix line endings, and also serves such data:
% GET -C 'user:password' https://caldav.example.org/username/calendar.ics/ | xxd | head -2 00000000: 4245 4749 4e3a 5643 414c 454e 4441 520a BEGIN:VCALENDAR. 00000010: 5052 4f44 4944 3a2d 2f2f 5261 6469 6361 PRODID:-//Radica
Note the 0x0a without the 0x0d at the end of the first line.
0x0a
0x0d
As a consequence, the iCalendar.org validator reports an error when passed the data served by Radicale (0.9-1+deb8u1)
You are using a very old version
So this is fixed in a later version? I looked but couldn't identify a changeset. Any hints?
Test pass when i upload a .ics file.
In RFC 5545, "3.1. Content Lines" it's written:
However, Radicale writes its files using Unix line endings, and also serves such data:
Note the
0x0a
without the0x0d
at the end of the first line.As a consequence, the iCalendar.org validator reports an error when passed the data served by Radicale (0.9-1+deb8u1)