-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.5 imap/http_caldav.c:caldav_put() ensure ORGANIZER is consistent #1768
Comments
@ksmurchison - what do you think of this? The patch is against 2.5 but it looks like it might apply to 3.0 too (with some finessing). I'm happy to do the wrangling if you're happy for it to be merged? |
If this is compliant with RFCs 5545, 5546, and 6638 then let's apply it to both 2.5 and 3.0 |
https://tools.ietf.org/html/rfc5545#section-3.8.4.3:
That's kind of ... unenlightening? Seems like this behaviour is neither explicitly verboten nor explicitly allowed I don't see anything in the other two RFCs regarding when organizer is/isn't appropriate (but I might have missed something, I'm not familiar with these in any depth) |
https://tools.ietf.org/html/rfc6638#section-3.2.4.2
|
Yes. That's the correct reference. The patch looks sane to me. |
Patch applied, thanks :) I copied your author line from one of your other commits, hope that's okay |
If the first element of a caldav object has no ORGANIZER, make sure that no other element of the same caldav object has an ORGANIZER (RFC 6638 Section 3.2.4.2 CALDAV:same-organizer-in-all-components Precondition)
The text was updated successfully, but these errors were encountered: