Version 5.4 |
|||||||||||||||||||||||||||||||||||
|
|
The WebDAV component provides a read-only "root" element, with the following URLs:
http://servername[:port]/
or
https://servername[:port]/ URL
where port is a HTTP User Module port (8100, 9100 by default).
Various WebDAV (CalDAV, CardDAV, etc.) clients can be configured to use this Root Element. They can retrieve the Root Element properties, which direct them to other URLs (realms), implementing the respective protocols.
The WebDAV protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel:
Use the RootDAV Log setting to specify the type of information the Root Element DAV module should put in the Server Log.
The Root Element DAV module records in the System Log are marked with the RootDAV tag.
The WebDAV protocol and protocols based on WebDAV allow users to access resources of other
users if the proper access rights have been granted.
To support WebDAV ACLs (Access Control Lists), each CommuniGate Pro users is granted a
unique URL that represents that user in the Access Control Lists. These URLs are:
http://servername[:port]/UserDAV/accountName@domainName
or
https://servername[:port]/UserDAV/accountName@domainName/ URL
where port is a HTTP User Module port (8100, 9100 by default).
The WebDAV protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel:
Use the UserDAV Log setting to specify the type of information the Principal Elements DAV module should put in the Server Log.
The Principal Elements DAV module records in the System Log are marked with the UserDAV tag.
The CommuniGate Pro Server implements access to Account File Storage via the WebDAV protocol (FileDAV).
All FileDAV data requests must be authenticated: the user should specify the Account name and password. The Account and its Domain must have the WebSite Service enabled.
The "root" of the user File Storage has the following URL:To Access the File Storage of some other user, the following URLs should be used:
The WebDAV protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel:
Use the FileDAV Log setting to specify the type of information the FileDAV module should put in the Server Log.
The FileDAV module records in the System Log are marked with the FileDAV tag.
The CommuniGate Pro Server supports the CalDAV protocol, a WebDAV protocol extension.
This protocol allows CalDAV clients to access and modify Calendaring and Tasks data stored in the user Account(s).
A full-featured CalDAV client can detect the proper URL for CalDAV operations
itself, when it is directed to the WebDAV Root element:
http://servername[:port]/
or
https://servername[:port]/ URL
where port is a HTTP User Module port (8100, 9100 by default).
If the mailboxName ends with the ics file extension, the Server removes that extension.
All CalDAV data requests must be authenticated: the user should specify the Account name and password. The Account and its Domain must have the WebCal Service enabled.
If the user Domain Name or Domain Alias name is mail.company.com, the HTTP User port is 80, and the Mailbox name is Calendar, the access URL isThe CalDAV protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel:
Use the CalDAV Log setting to specify the type of information the CalDAV module should put in the Server Log.
The CalDAV module records in the System Log are marked with the CalDAV tag.
The CommuniGate Pro HTTP User module implements an older, pre-CalDAV method of dealing with
data in Calendar and Task Mailboxes.
The module allows client applications to retrieve all items using the iCalendar format. This operation is often
called subscribing to Calendar data.
The module also allows client applications to rewrite
the Mailbox content new iCalendar-formatted data (to publish calendaring data).
All Calendaring data requests must be authenticated: the user should specify the Account name and password. The Account and its Domain must have their WebCal Service enabled.
If the user Domain Name or Domain Alias name is mail.company.com, the HTTP User port is 80, and the Mailbox name is Calendar, the access URL isSome applications do not support the DELETE method. These applications expect that the
PUT operation removes all previous information from the Calendar Mailbox.
To support these applications, use the CalendarDataDel realm instead of the CalendarData realm,
or include the DeleteAll="1" parameter into the URL.
In this case each PUT operation will be preceded with a virtual DELETE operation removing all existing iCalendar items from the Mailbox.
The CommuniGate Pro Server supports the CardDAV protocol, a WebDAV protocol extension.
This protocol allows CardDAV clients to access and modify Contacts data stored in the user Account(s).
A full-featured CardDAV client can detect the proper URL for CardDAV operations itself,
when it is directed to the WebDAV Root element:
http://servername[:port]/
or
https://servername[:port]/ URL
where port is a HTTP User Module port (8100, 9100 by default).
If the mailboxName ends with the vcf file extension, the Server removes that extension.
All CardDAV data requests must be authenticated: the user should specify the Account name and password. The Account and its Domain must have the WebSite Service enabled.
If the user Domain Name or Domain Alias name is mail.company.com, the HTTP User port is 80, and the Mailbox name is Contacts, the access URL isThe CardDAV protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel:
Use the CardDAV Log setting to specify the type of information the CardDAV module should put in the Server Log.
The CardDAV module records in the System Log are marked with the CardDAV tag.