9 Mar
2019
9 Mar
'19
1:27 p.m.
If an event has a LAST-MODIFIED:
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
this seems not to be recognized by InfCloud. As a result, when changing the
event via InfCloud, an additional LAST-MODIFIED is added:
LAST-MODIFIED:20190309T090207Z
...
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
Other caldav systems, e.g. ownCloud, then reject this event as being
invalid.
I'm not quite sure who to blame...
-- Johan
10 Apr
10 Apr
8:45 p.m.
Hi Johan,
I checked the source code and also tried the regexes related to date-time parsing and
everything looks OK. Can you please send me a private e-mail with an example ics file?
Cheers,
JM
p.s.: sorry for the late response, but it looks like your mail was marked as spam ;-)
On 9 Mar 2019, at 14:27, Johan Vromans
<jvromans(a)squirrel.nl> wrote:
If an event has a LAST-MODIFIED:
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
this seems not to be recognized by InfCloud. As a result, when changing the
event via InfCloud, an additional LAST-MODIFIED is added:
LAST-MODIFIED:20190309T090207Z
...
LAST-MODIFIED;VALUE=DATE-TIME:20190308T231001Z
Other caldav systems, e.g. ownCloud, then reject this event as being
invalid.
I'm not quite sure who to blame...
-- Johan
1450
days inactive
1482
days old
1 comments
2 participants
participants (2)
-
Johan Vromans -
Ján Máté