#386: DTSTAMP should be (partially) filtered in calendarDataMatch
----------------------------+-----------------------------------------------
Reporter: dou...@… | Owner: cda...@…
Type: Defect | Status: new
Priority: 5: Not set | Milestone:
Component: CalDAV Tester | Severity: Other
Keywords: |
----------------------------+-----------------------------------------------
DTSTAMP is equivalent to LAST-MODIFIED for entities without a METHOD so
should be filtered for those tests. For example, tests in put.xml fail
because the DTSTAMP value changes,
DTSTAMP from rfc5545:
{{{
Purpose: In the case of an iCalendar object that specifies a
"METHOD" property, this property specifies the date and time that
the instance of the iCalendar object was created. In the case of
an iCalendar object that doesn't specify a "METHOD" property, this
property specifies the date and time that the information
associated with the calendar component was last revised in the
calendar store.
...
In the case of an iCalendar object that specifies a "METHOD"
property, this property differs from the "CREATED" and "LAST-
MODIFIED" properties. These two properties are used to specify
when the particular calendar data in the calendar store was
created and last modified. This is different than when the
iCalendar object representation of the calendar service
information was created or last modified.
In the case of an iCalendar object that doesn't specify a "METHOD"
property, this property is equivalent to the "LAST-MODIFIED"
property.
}}}
--
Ticket URL: <http://trac.calendarserver.org/ticket/386>
Calendar and Contacts Server </>
HTTP/WebDAV/CalDAV Server
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev
