Specifications

HTTP/HTTPS Access
Chapter 2 Network Access to the Server 37
HTTP/HTTPS Access
HTTP and HTTPS are used for browser-based access to the server via Web View,
Web Root, or the Administration UI. HTTPS enhances security by encrypting
communications between client and server, and cannot be disabled. You can,
however, disable HTTP access on the
Network > Web screen of the Administration
Tool. Additionally, you can require browser-based clients to authenticate to the
server.
Note To access the CA eTrust Antivirus configuration interface (on the
Snap
Extensions
screen), HTTP must be enabled.
GuardianOS supports the following browers: Microsoft Internet Explorer (6.0 or
later), Apple Safari (2.0 or later), and Mozilla FireFox (2.0 or later).
Configuring HTTP/HTTPS
You can require web authentication, disable http (non-secure) access, and enable
the Web Root feature.
Using WebRoot to Configure the SnapServer as a Simple Web Server
When you enable the Web Root feature from the Network > Web page, you can
configure your SnapServer to open automatically to an html page of your choice
when a user enters
http://[servername] or http://[IP address] in the
browser field.
In addition, files and directories underneath the directory you specify as the Web
Root can be accessed by reference relative to
http://[servername] without having
to reference a specific share. For example, if the Web Root points to directory
WebRoot on share SHARE1, the file SHARE1/WebRoot/photos/slideshow.html can be
accessed from a web browser as
http://[servername]/photos/slideshow.html.
The Web Root can also be configured to support directory browsing independent of
Web View (access through shares).
Note The SnapServer supports direct read-only web access to files. It is not
intended for use as an all-purpose Web Server, as it does not support PERL or Java
scripting, animations, streaming video, or anything that would require a special
application or service running on the server.