File Sites |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
Personal File Sites use the same HTTP port as the WebUser Interface (the port 8100 by default).
In addition to the ~ prefix, an alternative prefix can be specified in the Domain Settings. The alternative prefix can be an empty string.
All Routing Rules discussed in the Access section apply to the Personal File Site URLs, so Account and Domain aliases can be used in the Personal File Site URL.
Personal File Site can be accessed without a prefix, using just the server part of the URL string. When the CommuniGate Pro server receives an HTTP connection on the its WebUser port, it uses the special Domain Routing procedure.
If the domain name user.domain.com has a DNS A-record pointing to the IP address of the CommuniGate Pro
server, and the CommuniGate Pro Router has the following record:
<LoginPage@user.domain.com> = userA@domainB.com
and the Account userA exists in the CommuniGate Pro Domain domainB,
then the URL http://user.domain.com/ can be used to access the Personal File Site
of the userA@domainB.com Account.
Personal File Sites must not contain any index.wssp file. This name is reserved for the File Site Management forms.
The home (default) page of a Personal File Site should have the default.html name. This means that when the file name is not specified explicitly, the default.html name is assumed. If a File Site has folders (subdirectories), then the request with the http://server:port/prefix user/folder/ URL retrieves the default.html file from that subdirectory.
The name of the default page is specified as an Account Setting and it can be modified on the per-Account basis.
The private folder can be used as a repository for any type of documents - the user can access them from anywhere, using any browser.
Server administrators with the All Domains and Accounts Access Right and Domain administrators with the CanAccessWebSites access right can access File Sites belonging to other users. They can use the same URL, opening the Index.wssp file, but they should provide their own account names and passwords.
Server and Domain administrators can access other users Personal File Site using the WebAdmin Interface: the Account management pages have the Files link in their navigation panels.
All management methods use similar HTML pages for File Site administration:
Click the Browse button and select a file you want to upload to the File Site. Click the Upload File button to upload the file. Its name should appear in the list.
Select the checkboxes to mark the files and/or folders you want to remove from the Personal File Site and click the Delete Marked button. The selected files will be removed.
Type in a name and click the Create Folder button to create a folder (sub-directory) in the Personal File Site.
Select exactly one checkbox to mark the file or folder you want to rename, and enter a new name for it in the field next to the Rename Marked button. Click the Rename Marked button to rename the selected file or folder.
Click the file name link to open the file. Click the folder name link to open the subdirectory. When a subdirectory is opened, its name is displayed on the top of the file list. Click the UP link to open the parent subdirectory.
The This Folder line displays the total number of files and folders, and the total size of all files in the opened folder. The Totals line displays the total number of files and folders, and the total size of all files in the Personal File Site. The limits line displays the specified maxmimum number of files and folders and the specified maxmimum total file size for this Personal File Site.
The same is true for all Personal File Site subfolders: http://server:port/~username/subfolder/
is the same as http://server:port/~username/subfolder/default.html
The name of the default file can be changed on the per-Account basis, by modifying the Account Settings.
If the Free/Busy information cannot be built (for example, if no Main Calendar mailbox exists in the Account), the HTTP module generates an empty Free/Busy dataset and sends it to the client.