System Administrator
The System Administrator username is used to access these sysadmin folder
and administrator methods. By default, the administrator username is 'admin'.
System Administrator IP
If left blank, the Sambar Server System Administrator may login from
any host. A space-separated list of IP addresses may be provided
(the wild-card character '*' may be used, i.e. 140.172.165.* ) to ensure
that only hosts which you plan to use for administration have access to
your System Administration tools. For maximum security, only allow access
to the "localhost" account (127.0.0.1).
User IP
If left blank, Sambar Server users may login from any host.
A space-separated list of IP addresses may be provided (the wild-card
character '*' may be used, i.e. 140.172.165.* ) to ensure
that only hosts which you plan to use for user logins have access to
your server.
Server Port
The TCP/IP protocol has a number of ports which are used to differentiate
requests to different processes. The standard HTTP port number is 80. You can
choose any port number from 1 to 65000, however, many port numbers on your
system are reserved for other applications. Should you choose any port other
than port 80, you will have to access you homepage with the port number
appended to the URL (i.e. http://www.sambar.com:1080/ ).
Security Realm
The security realm of the server. This applies to all Basic
security.
NT Authentication
>
Yes >
No
Perform username/password authentication using NT Authentication/domain.
By default, the Sambar Server config/passwd file is used.
NT Authentication is not recommended for servers that will reside
on the internet.Domain Radius Authentication
>
Yes >
No
Perform username/password authentication using a Radius server.
Important! Radius authentication is still being debugged.
To override the default radius port (1812), specify the radius host
as hostname :port . By default, the Sambar Server
config/passwd file is used.Server Secret Maximum Connections
Configure the maximum simultaneous connections supported by the system.
Connections differ from users in that a connection is only maintained
by the HTTP server for the duration of the transaction (HTTP request).
Therefore, while you might wish to support 200 simultaneous users, the
number of simultaneous connections needed to support that number of users
would likely be no more than 20.
Network Read Timeout
Configure the maximum time, in seconds, to wait for a client connection
before terminating the connection. This period must be at least as
large as the Keep-Alive duration defined for the HTTP protocol. This
duration affects HTTP, proxy and FTP clients.
Memory Cache
Configure the size, in bytes, for in-memory caching of disk files.
If zero (0) is specified, no file caching is performed. The memory cache
is used to enhance the HTTP Server performance only; there is presently
no caching mechanism for HTTP Proxy requests. For maximum performance,
this should be set to the cumulative size of all static files in your
document directories. (Note: The FTP Server and DNS Server also use this
memory cache).
Resolve Host Names
>
Yes >
No
Configure the server to perform a DNS lookup on every host connection
to resolve the hostname. WARNING: This requires communicating with
a DNS server which can be quite slow if not properly configured. You
should absolutely NOT turn this feature on if your DNS server is on the
other side of a WAN, modem dial-up, or if you expect user heavy traffic.
Automatic Directory Lists
>
Yes >
No
If no default index page is present, this boolean indicates whether
the server should display the contents of the directory.
Enforce .htaccess
>
Yes >
No
HTAccess Authentication was first implemented in NCSA and has since
become a de-facto standard for file-based access authentication. See the
documentation for additional information on this functionality.
CGI stderr
>
Yes >
No
If turned on, the CGI STDERR output is returned to the client as received
from the CGI application. In false (the default), only CGI STDOUT output is
returned to the client.
ISAPI Debug Level
SELECTED> None
SELECTED> Basic
SELECTED> Call
SELECTED> Full
The debug level for ISAPI applications.
None : No logging of any kind.
Basic : Log only ISAPI function failures.
Call : Trace all ISAPI function calls.
Full : Detailed trace of each ISAPI call (for developers only).
Automatic Log Rotation
SELECTED> No log rotation
SELECTED> Rotate Daily
SELECTED> Rotate Weekly
SELECTED> Rotate Monthly
If turned on, the server log files (www, proxy, mail, dhcp etc.) will be
automatically rotated and a WWW log report will be automatically run.
The log reports are available through the system administration Report
interface.
Home Page
The HTTP document served when users request the home page (/) from the server.
Default Page(s)
The HTTP page served when users request a page from a directory without
specifying a path to a URL. This can be a space separated list of file
names (i.e. index.htm index.html index.shtml).
Documents Directory
The directory in which documents are served out of. If not preceded by
a drive letter (i.e. d:\wwwdir), this directory is assumed to be relative to
the installation directory of the Sambar Server ().
CGI Directory
The directory in which cgi-bin scripts are served out of. The
CGI directory must be found in the installation directory of the
Sambar Server. The Sambar Server CGI plug-in module can be used to
execute CGI applications outside the CGI directory.
WinCGI Directory
The directory in which Windows CGI scripts are served out of. The
WinCGI directory must be found in the installation directory of the
Sambar Server. The Sambar Server WinCGI plug-in module can be used to
execute WinCGI applications outside the WinCGI directory.
ISAPI Extensions
This should be a space separated list of ISAPI extensions that, if found
in the Documents Directory should be recognized as a DLL with
ISAPI extensions executed (i.e. *.dll).
If left blank, ISAPI extension cannot be run in the Doucments
Directory (with the exception of any direct execute ISAPI DLLs found
in the [isapi] section).
CGI Extensions
This should be a space separated list of CGI extensions that, if found
in the Documents Directory should be recognized as CGI scripts and
executed (i.e. *.cgi *.exe *.pl).
If left blank, only scripts found in the CGI Directory are
treated as CGI scripts.
WinCGI Extensions
This should be a space separated list of WinCGI extensions that, if found
in the Documents Directory should be recognized as CGI scripts and
executed (i.e. *.cgi *.exe).
If left blank, only scripts found in the WinCGI Directory are
treated as WinCGI scripts.
Server Side Includes
A space separated list of HTML file extensions that correspond with
files containing server side includes (i.e. shtml sht). As parsing
server-side include files is expensive, it is recommended that the
extensions be limited to shtml .
Prohibit Script #exec
>
Yes >
No
Server-side include scripts may contain #exec directives that execute
arbitrary server-side scripts. If untrusted users are permitted to upload
documents to your server, you should prohibit the use of this directive.
Log Format
SELECTED> Sambar Server Format
SELECTED> NCSA Combined Log Format
SELECTED> NCSA Common Log Format
The log format options are:
performance - Sambar Server performance format
combined - NCSA combined log format
common - NCSA Common Log Format
Don't Log IPs
A space separated list of IP addresses not to log requests from.
This list may use wild-cards to match against (i.e. 127.0.0.1 140.172* ).
Don't Log Requests
A space separated list of requests not to log.
This list may use wild-cards to match against (i.e. *.jpg *.gif /foo* ).
Log Buffer Size
Configure the maximum number of lines permitted in the server log
file (server.log). Once this number is reached for a server session,
the log is reset to the first line (it operates much like a circular buffer).
For an infinite log size, set the log size value to 0.
Compress Content
>
Yes >
No
Enable compression of content
served up by the Sambar Server.
Enable ASP Engine
>
Yes >
No
Enable the ASP/CScript Engine
in the Sambar Server.
Enable WebDAV
>
Yes >
No
Enable the experimental WebDAV and
versioning functionality in the Sambar
Server. Enabling WebDAV results in significant enhancement to the
Document Manager.
Enable JavaEngine
>
Yes >
No
Enable the Sambar Server JavaEngine module. The JavaEngine implements
the Java 1.2 Servlet interface. See the
JavaEngine Help pages for configuration
help. The Sun Java JDK must be installed prior to enabling this
functionality.
Enable DBMS Usage
>
Yes >
No
Enable the DBMS interface of the Sambar Server. The DBMS interface
must be initialized to use the DBMS scripting. Once configured, the
DBMS management interfaces become available in the System Administration
console. (Note: You must have ODBC installed to enable this option.)
Act as HTTPS Server
>
Yes >
No
Start the SSL HTTP Server when the Sambar Server is started (in addition
to the HTTP server). There are several additional configuration elements
associated with installing and running SSL on the Sambar Server.
See the SSL documentation for more details.
Act as Mail Server
>
Yes >
No
Start the Mail Server when the Sambar Server is started (in addition
to the HTTP server). Additional Mail configuration parameters must be
entered via the Mail Configuration forms on the System Administration
pages. User mailboxes are created using the User Management forms.
WARNING: At this time, the Mail Server is not mature and
should not be used in production environments.
Act as DNS Server
>
Yes >
No
Start the DNS Server/Proxy when the Sambar Server is started.
Additional DNS configuration parameters must be entered via the
DNS Configuration forms on the System Administration pages.
The functionality of this server/proxy is outlined on the
DNS system help pages.
Act as FTP Server
>
Yes >
No
Start the FTP Server when the Sambar Server is started (in addition
to the HTTP server). WARNING: If your machine is already running an
FTP Server, the FTP Server will fail to start if the ports of the two
servers conflict.
Act as TFTP Server
>
Yes >
No
Start the TFTP Server when the Sambar Server is started (in addition
to the HTTP server). WARNING: If your machine is already running an
TFTP Server, the TFTP Server will fail to start if the ports of the two
servers conflict. The TFTP supports read-only access to files
found in the Sambar Server tftpboot directory.
Act as Telnet Server/Proxy
>
Yes >
No
Start the Telnet Server & Proxy when the Sambar Server is started
(in addition to the HTTP server). See the
Telnet documentation for usage details.
Run Watcher
>
Yes >
No
Start a Watcher Daemon when the server is started to monitor the
WWW server and restart it in the event of a failure. This feature can
be used when the Sambar Server is run as an NT Service.
Watcher Timeout
Configure the delay in seconds between each wwwping of the server
by the watcher daemon. This time should exceed 60 seconds (300 is the default).
After two consecutive connect failures, the Sambar Server will be terminated
and restarted by the Watcher Daemon.
NTP Server Specify an NTP server (network time protocol) to use to synchronize
the server's clock with at the specified cron period. See
www.ntp.org for a list of public NTP
servers. If the NTP server
or cron period is left blank, synchronization will not occur. An example
cron period would be 0 1 * * * , which equates to every nigth at 1AM.
Cron
