|
Version 6.3 |
|
| ||||||||||||||||||||||
Root ElementThe WebDAV component provides a read-only "root" element, with the following URLs:
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. Configuring the Root Element ModuleThe 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 Level setting to specify the type of information the Root Element DAV module should put in the Server Log.
The Access setting specifies who can access the RootDAV service. Principal ElementsThe WebDAV protocol and protocols based on WebDAV allow users to access resources of other
users if the proper access rights have been granted.
Configuring the Principal Elements DAV ModuleThe 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 Level setting to specify the type of information the Principal Elements DAV module should put in the Server Log.
The Access setting specifies who can access the Principal Elements DAV Module service. File AccessThe 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:http://servername[:port]/WebDAV/ or https://servername[:port]/WebDAV/ where port is a HTTP User Module port (8100, 9100 by default). To Access the File Storage of some other user, the following URLs should be used: http://servername[:port]/WebDAV/~accountName/ or https://servername[:port]/WebDAV/~accountName/ where port is a HTTP User Module port (8100, 9100 by default), and the accountName is the name of the Account to access. If this Account is located in a different Domain, use accountName@domainName instead. Configuring the FileDAV ModuleThe 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 Level setting to specify the type of information the FileDAV module should put in the Server Log.
The Access setting specifies who can access the FileDAV service. CalDAVThe 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:
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 is
Configuring the CalDAV ModuleThe 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 Level setting to specify the type of information the CalDAV module should put in the Server Log.
The Access setting specifies who can access the CalDAV service. Using the Publish/Subscribe (ICS) methodThe CommuniGate Pro HTTP User module implements an older, pre-CalDAV method of dealing with
data in Calendar and Task Mailboxes.
If the mailboxName ends with the ics file extension, the server removes that extension. If the mailboxName is empty, the Server uses the Default Calendar name. 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 is
Some applications do not support the DELETE method. These applications expect that the
PUT operation removes all previous information from the Calendar Mailbox.
CardDAVThe 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:
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 is
Configuring the CardDAV ModuleThe 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 Level setting to specify the type of information the CardDAV module should put in the Server Log.
The Access setting specifies who can access the CalDAV service. |