CalDav Support: Difference between revisions
Gren Elliot (talk | contribs) |
Gren Elliot (talk | contribs) |
||
Line 9: | Line 9: | ||
'''Warning:This is a work in progress''' | '''Warning:This is a work in progress''' | ||
{| class="wikitable" | |||
! style="text-align:left;"| Standard ID | |||
! URL | |||
! Description | |||
|- | |||
| RFC 5545 | |||
| https://tools.ietf.org/html/rfc5545 | |||
| Internet Calendaring and Scheduling Core Object Specification (iCalendar) | |||
|- | |||
| RFC 4918 | |||
| https://tools.ietf.org/html/rfc4918 | |||
| HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) | |||
|- | |||
| RFC 4791 | |||
| https://tools.ietf.org/html/rfc4791 | |||
| Calendaring Extensions to WebDAV (CalDAV) | |||
|- | |||
| RFC 6638 | |||
| https://tools.ietf.org/html/rfc6638 | |||
| Scheduling Extensions to CalDAV | |||
|- | |||
| RFC 5995 | |||
| https://tools.ietf.org/html/rfc5995 | |||
| Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections | |||
This is the preferred mechanism for creating new entries in the calendar. Using the PUT | |||
method with a final name that doesn't strictly match the form "<UID>.ics" will always fail. | |||
Using POST allows the server to choose the final name. | |||
|- | |||
| RFC 5397 | |||
| https://tools.ietf.org/html/rfc5397 | |||
| WebDAV Current Principal Extension | |||
|- | |||
| RFC 5689 | |||
| https://tools.ietf.org/html/rfc5689 | |||
| Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV) | |||
This is the preferred way to create new calendars | |||
|- | |||
| RFC 3253 (partial) | |||
| https://tools.ietf.org/html/rfc3253 | |||
| Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) | |||
See Section 3.6 (Report method) and 3.8 (DAV:expand-property Report) | |||
|- | |||
| RFC 3744 | |||
| https://tools.ietf.org/html/rfc3744 | |||
| Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol | |||
|} | |||
== Client configuration == | == Client configuration == |
Revision as of 14:11, 13 April 2017
CalDAV Support
{{KB ZCS 8.0 }}
- This article is a Work in Progress, and may be unfinished or missing sections.
RFCs supported by Zimbra's CalDAV implementation
Warning:This is a work in progress
Standard ID | URL | Description |
---|---|---|
RFC 5545 | https://tools.ietf.org/html/rfc5545 | Internet Calendaring and Scheduling Core Object Specification (iCalendar) |
RFC 4918 | https://tools.ietf.org/html/rfc4918 | HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) |
RFC 4791 | https://tools.ietf.org/html/rfc4791 | Calendaring Extensions to WebDAV (CalDAV) |
RFC 6638 | https://tools.ietf.org/html/rfc6638 | Scheduling Extensions to CalDAV |
RFC 5995 | https://tools.ietf.org/html/rfc5995 | Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections
This is the preferred mechanism for creating new entries in the calendar. Using the PUT method with a final name that doesn't strictly match the form "<UID>.ics" will always fail. Using POST allows the server to choose the final name. |
RFC 5397 | https://tools.ietf.org/html/rfc5397 | WebDAV Current Principal Extension |
RFC 5689 | https://tools.ietf.org/html/rfc5689 | Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)
This is the preferred way to create new calendars |
RFC 3253 (partial) | https://tools.ietf.org/html/rfc3253 | Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)
See Section 3.6 (Report method) and 3.8 (DAV:expand-property Report) |
RFC 3744 | https://tools.ietf.org/html/rfc3744 | Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol |
Client configuration
- How to configure Mac OS Calendar to access all your Zimbra Calendars
- How to configure Thunderbird's Lightning plugin to access an individual Zimbra Calendar
Historical CalDAV support
Older versions of Zimbra used a radically different mechanism for supporting CalDAV - see Historical CalDAV Support