Address book server7/6/2023 ![]() Which is shared between the CardDAV and CalDAV specifications. Bootstrapping of CardDAV URLs must take place according to section 6 ofĬaldav-ctag-02: Calendar Collection Entity Tag (CTag) in CalDAV,.rfc6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV).Google does not support any other authentication method.įor security of contact data, we require CardDAV connections to use Supports authenticating CardDAV client programs using OAuth 2.0 HTTPĪuthentication.Rfc6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage rfc6749: The OAuth 2.0 Authorization Framework and.Client applications must switch to this mode of operation after the.rfc6578: Collection Synchronization for WebDAV.Supports providing a principal collection and a contacts collection.Supports the HTTP method REPORT, but not all defined reports are.rfc6352: CardDAV: vCard Extensions to Web Distributed Authoring and.Supports creating new contacts without specifying an ID.rfc5995: Using POST to Add Members to WebDAV Collections.Does not support WebDAV Access Control (rfc3744).Does not support arbitrary (user-defined) WebDAV properties.Does not support the HTTP methods LOCK, UNLOCK, COPY, MOVE, or.Supports the HTTP methods GET, PUT, DELETE, OPTIONS, and. ![]() rfc2518: HTTP Extensions for Distributed Authoring (WebDAV).The full specification is not implemented, but many clients such asįor each relevant specification, Google's CardDAV support is as follows: Your client application can use the CardDAV API toĬreate new contacts, edit or delete existing contacts, and query for contacts ![]() You can view and manage your contacts using Google's CardDAV protocol.Ĭontacts are stored in the user's Google Account most Google services haveĪccess to the contact list. ![]()
0 Comments
Leave a Reply. |