#273: `valid-calendar-object-resource` precondition failure returns with a `403 FORBIDDEN`, should be `412 PRECONDITION FAILED` --------------------------------+------------------------------------------- Reporter: wsanchez@apple.com | Owner: cdaboo@apple.com Type: Defect | Status: closed Priority: 3: Important | Milestone: 1.x Component: Calendar Server | Version: Severity: Other | Resolution: worksforme Keywords: | --------------------------------+------------------------------------------- Comment (by mail@david-reid.com): Replying to [comment:3 cdaboo@apple.com]:
There are two types of "precondition" being used:
1) The HTTP If-Match/If-None-Match pre-condition behavior using ETags. An error with one of those should return a 412. I believe it does.
2) A WebDAV pre-condition/post-condition DAV:error response. Those should return a 403 - again I believe that is working fine. Check the latest WebDAV spec RFC4918 to see how those are used. The problem here is that the term "precondition" is being used in two different ways.
I am going to mark this as "worksforme" - if you disagree with my analysis go ahead and change it back with an explanation...
What sections of the RFC's are you looking at? -- Ticket URL: <https://trac.calendarserver.org/ticket/273#comment:4> CalendarServer </> HTTP/WebDAV/CalDAV Server