Difference between revisions of "CalDav Support"
| (15 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{BC|Community Sandbox}} | |
| + | __FORCETOC__ | ||
| + | <div class="col-md-12 ibox-content"> | ||
| + | =CalDAV Support= | ||
| + | {{KB{{ZCS 8.7}}}} | ||
| − | + | == RFCs supported by Zimbra's CalDAV implementation == | |
| + | {| 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 2616 | ||
| + | | https://tools.ietf.org/html/rfc2616 | ||
| + | | Hypertext Transfer Protocol -- HTTP/1.1 | ||
| + | |- | ||
| + | | RFC 2617 | ||
| + | | https://tools.ietf.org/html/rfc2617 | ||
| + | | HTTP Authentication: Basic and Digest Access Authentication | ||
| + | |- | ||
| + | | 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 6764 | ||
| + | | https://tools.ietf.org/html/rfc6764 | ||
| + | | Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV) | ||
| + | The Zimbra server implements the well-known URI for CalDAV. See section 9.1.1. | ||
| + | This specification can also be useful as a reference for how to configure DNS to make | ||
| + | client configuration easier. | ||
| + | |- | ||
| + | | 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 | ||
| + | |- | ||
| + | | draft-daboo-caldav-extensions-01 | ||
| + | | https://tools.ietf.org/html/draft-daboo-caldav-extensions-01 | ||
| + | | Section 4 - supported-calendar-component-sets | ||
| + | We use this because our calendar collections are typed. They can contain either | ||
| + | events or tasks but not both. | ||
| + | |- | ||
| + | | 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 | ||
| + | |- | ||
| + | | caldav-proxy (Apple extension) | ||
| + | | https://github.com/apple/ccs-calendarserver/blob/master/doc/Extensions/caldav-proxy.txt | ||
| + | | Calendar User Proxy Functionality in CalDAV | ||
| + | |} | ||
| − | + | === Known limitations === | |
| − | + | # Attachments are not currently supported via the CalDAV API. Attachments created by other Zimbra APIs are ignored within CalDAV. | |
| + | # New Calendar items cannot be created via PUT to a URL unless the component of the URL matches the form <UID>.ics where <UID> is the iCalendar UID of the calendar data being created. | ||
| − | + | == Client configuration == | |
| + | * [[Accessing_Zimbra_Collaboration_Server_with_iCal_and_Calendar|How to configure Mac OS Calendar to access all your Zimbra Calendars]] | ||
| + | * [[Accessing_Zimbra_Collaboration_Server_with_Thunderbird#Viewing_your_Zimbra_Calendar_using_Lightning|How to configure Thunderbird's Lightning plugin to access an individual Zimbra Calendar]] | ||
| + | *[https://www.davx5.com]https://www.davx5.com | ||
| + | *[https://play.google.com/store/apps/details?id=at.bitfire.davdroid]https://play.google.com/store/apps/details?id=at.bitfire.davdroid | ||
| + | *[https://f-droid.org/de/packages/at.bitfire.davdroid/]https://f-droid.org/de/packages/at.bitfire.davdroid/ | ||
| + | *[https://www.davx5.com/tested-with/zimbra]https://www.davx5.com/tested-with/zimbra | ||
| + | == Historical CalDAV support == | ||
| + | |||
| + | Older versions of Zimbra used a radically different mechanism for supporting CalDAV - see [[Historical_CalDAV_Support|Historical CalDAV Support]] | ||
| + | |||
| + | {{Article Footer|Zimbra Collaboration 8.7|04/06/2017}} | ||
[[Category:Clients]] | [[Category:Clients]] | ||
| + | [[Category:Architecture and Components]] | ||
Latest revision as of 09:53, 25 February 2021
Contents
CalDAV Support
{{KB
ZCS 8.7
}}
RFCs supported by Zimbra's CalDAV implementation
| Standard ID | URL | Description |
|---|---|---|
| RFC 5545 | https://tools.ietf.org/html/rfc5545 | Internet Calendaring and Scheduling Core Object Specification (iCalendar) |
| RFC 2616 | https://tools.ietf.org/html/rfc2616 | Hypertext Transfer Protocol -- HTTP/1.1 |
| RFC 2617 | https://tools.ietf.org/html/rfc2617 | HTTP Authentication: Basic and Digest Access Authentication |
| 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 6764 | https://tools.ietf.org/html/rfc6764 | Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
The Zimbra server implements the well-known URI for CalDAV. See section 9.1.1. This specification can also be useful as a reference for how to configure DNS to make client configuration easier. |
| 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 |
| draft-daboo-caldav-extensions-01 | https://tools.ietf.org/html/draft-daboo-caldav-extensions-01 | Section 4 - supported-calendar-component-sets
We use this because our calendar collections are typed. They can contain either events or tasks but not both. |
| 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 |
| caldav-proxy (Apple extension) | https://github.com/apple/ccs-calendarserver/blob/master/doc/Extensions/caldav-proxy.txt | Calendar User Proxy Functionality in CalDAV |
Known limitations
- Attachments are not currently supported via the CalDAV API. Attachments created by other Zimbra APIs are ignored within CalDAV.
- New Calendar items cannot be created via PUT to a URL unless the component of the URL matches the form <UID>.ics where <UID> is the iCalendar UID of the calendar data being created.
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
- [1]https://www.davx5.com
- [2]https://play.google.com/store/apps/details?id=at.bitfire.davdroid
- [3]https://f-droid.org/de/packages/at.bitfire.davdroid/
- [4]https://www.davx5.com/tested-with/zimbra
Historical CalDAV support
Older versions of Zimbra used a radically different mechanism for supporting CalDAV - see Historical CalDAV Support
