Sun WebServer 2.1 Command Reference

Previous: man Pages(1m): Maintenance Commands

man Pages(4): File Formats

htIntro(4)

NAME

^TM

DESCRIPTION

The configuration and log files are available to configure and monitor Sun WebServer.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhtman
Interface Stability	Evolving

FILES

The following files are used by the command-line utilities:

access.conf: Configures a web site's access control lists (ACLs) . Located at site_path/conf/access.conf.
access.conf: Configures the server administration ACLs. Located at /etc/http/access.conf.
content.conf: Defines the content variants, encoding types, and directory preferences for a web site. Located at site_path/conf/content.conf.
httpd-instances.httpd.conf: Tracks all Sun WebServer instances. When htserver creates a new server instance, an entry is added to this file. Located at /etc/http/httpd-instances.httpd.conf.
site_name.site.conf: Contains the web site servlet engine configuration if the servlet engine is not shared. Located at site_path/conf/site_name.site.conf.
instance_name.httpd.conf: Defines the server instance's configuration. When hthost adds a new site, it creates an entry in httpd.conf to define the site_path and web site configuration file. Located at /etc/http/instance_name.httpd.conf.
map.conf: Creates an alias to a path on the file system or a redirection to a remote URL from a Uniform Resource Identifier (URI) on the host. Located at site_path/conf/map.conf.
realms.conf: Defines realms of user and group information used by access control lists on a Sun WebServer web site. Located at site_path/conf/realms.conf.
servlets.properties: Defines each servlet that can be loaded by a web site. Located at site_path/conf/servlets.properties.

NOTES

access.conf: Defines ACLs for the content hosted by a web site. ACLs regulate access to resources on the site by defining which users, groups, and/or hosts have permissions to make HTTP GET, PUT, POST, and DELETE requests.
content.conf: Represents meta-data for directories, site preferences for languages, media and encoding types, and specifying variants for content.
httpd-instances.httpd.conf: Associates each unique httpd process (or server instance) with its configuration file, and defines whether or not a server instance is enabled.
httpd.cgi.logs: Logs errors generated by CGI scripts. Log files will be named prefix.sequence, where sequence is a cycling number.
httpd-instances.httpd.conf: The server instance configuration file contains directives that define the server's runtime behavior, the web sites it hosts, and the network connection end points it uses.
httpd.event.logs: The server events log files. The httpd server puts out error messages and warnings via syslogd to /var/adm/messages by default.
httpd.request.logs: Logs all incoming requests to a server activity log file. Sun WebServer generates log files using one of three log file formats configurable by the administrator.
httpd.servlet.logs: Logs errors generated by servlets. Log files will be named prefix.sequence, where sequence is a cycling number.
site_name.site.conf: The sites instance configuration file contains directives that define the site's runtime behavior, and defines the identity and server resources used by a web site hosted by the server instance. This file defines properties such as the web site's canonical host name and aliases, the location of the configuration files, and the network connections available to the web site, and defines the servlet engine settings for the web site.
instance_name.httpd.conf: The server instance's configuration file contains directives that define the server's runtime behavior, and defines the web sites hosted on the server. When hthost adds a new site, it creates an entry in httpd.conf to define the site_path and web site configuration file.
map.conf: A map directive allows you to redirect requests for a URL on a host to any other URL or to a different directory.
realms.conf: Defines realms of user and group information used by access control lists on a Sun WebServer web site. A realm defines a protection space, a domain of users and groups and their permissions.
servlets.properties: Defines the servlet properties file in a general Java properties file format. The file contains the name of each servlet and the initialization parameters of the servlet.

Sun WebServer 2.1 Last Revised 22 February 1999

access.conf(4)

NAME

^TM

SYNOPSIS

site_path/conf/access.conf - Web site access control lists.

/etc/http/access.conf - Global access control lists for administration

DESCRIPTION

The access.conf file defines access control lists (ACLs) for the content (represented as URI) hosted by a web site. ACLs regulate access to resources on the site by defining which users, groups, and/or hosts have permission to make HTTP GET, PUT, POST, and DELETE requests. ACLs also determine which users, groups, and/or hosts have permission to modify the ACL itself.

ACL definitions may be created by htaccess(1m), by the Sun WebServer GUI, or by Apache Emulator for FrontPage publishing tools.

Note -

If FrontPage publishing is active for a site, do not edit the access.conf file. FrontPage must be able to read and write the ACL information in a form that it can use, and manual edits may interfere with FrontPage's ability to manage ACL information.

Each ACL definition in the file consists of the following:

Realm used to store information about valid users.
Authentication scheme used to ask clients for password information.
List of users and/or groups in the realm who have permission to change the ACL definition.
HTTP method block or blocks defining the access permissions on the URI for the given methods.
Optionally, URI of the resource using the ACL. If the URI is not specified, it applies to all the URIs under this site.
Optionally, ACL definition blocks for URIs beneath the current one in the document root. These definitions assume the definition of the parent block; explicit directives change the definition in the child block and its children.

Syntax

The following syntax rules apply to the access.conf file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored.
White space is ignored in directive definitions.
A string with a space must be inside double quotes.
Some directives accept a list of values. Separate multiple values by white space. If more than one line is required to list all values, escape all but the last new line with a backslash (\) at the end of the line.
All directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, new lines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks that also use matched curly braces to contain a definition.
ACL definitions (url { } blocks) may be nested within other definitions, as long as the nesting matches the actual URI hierarchy. You cannot nest url /parent/subdir { ... url /parent { ... } }. The nested URL is always treated as a path relative to the parent URL.
The ACL definition on a given URI inherits directives from ACLs on parent URIs, even if the blocks are not nested.

Each ACL definition is in the following form:

url <URI> {
   [ realm <realm_name> ]
   [ authentication_scheme <auth_scheme> ]
   [ administrator {
      user <realm_user>[ <realm_user>]...
      [ group <realm_group>[ <realm_group>]... ]
   } ]
   [ method <method_list> {
      [ + | - group * | <realm_group>[ <realm_group>]... ]...
      [ + | - host * | <host>[ <host>]... ]...
      [ + | - user * | <realm_user>[ <realm_user>]... ]...
   } ]...
   [ url <URI> { <ACL> } ]...
}

The syntax and definition of each directive and block is explained in the following Directives section. Note that all directives are optional. Unless a directive is explicitly defined, its value is inherited from the ACL on the parent URI. If there is no value defined in the parent URI ACL (or any of its parents), the following defaults apply:

realm: There is no default. If no realm can be defined, then all user and group directives are ignored.
authentication_scheme: If you do not change the default of no authentication_scheme, then all user and group directives are ignored.
method: Defaults to ALL.
group: Defaults to + group *, meaning any authenticated member of any group in the realm is allowed access unless another directive explicitly denies access.
host: Defaults to + host *, meaning connections are allowed from any host name.
user: Defaults to + user *, meaning any authenticated used defined in the realm is allowed access unless another directive explicitly denies access.
administrator: Defaults to either the site or the server administrator. A site administrator is the principal with access to the pseudo-URI "/sws_administration" in the site-level access.conf. Similarly, a server administrator is a principal with access to the pseudo-URI "/sws_administration" in the global access.conf.

Directives

The following keyword directives are valid in the access.conf file:

administrator { admins }

Names users and groups in the specified realm with permissions to change or delete the ACL through the Sun WebServer GUI or the htaccess(1m) utility. The directive admins may contain a user directive or optionally a group directive:

user realm_user[[ realm_user]]...: Defines ACL administrators. User names must be valid in the ACL's realm.
group realm_group[[ realm_group]]...: Defines groups whose members have permission to change or delete the ACL. Group names must be valid in the ACL's realm.

authentication_scheme basic | md5 | none

Defines the encoding of authentication information for the ACL where basic means user name and password information should be sent in BASE64 encoding over HTTP; md5 means the server exchanges a message digest of certain header fields and the password is never sent over the wire; and none means that no authentication scheme will be used.

method method[ method]... { permissions }

Defines a block of permissions that regulate access to the named resource for the HTTP methods listed. The method can be ALL meaning any method, or it can be a list of one or more of: DELETE, GET, POST, or PUT. The permissions regulate access to the resource by realm user name, realm group name, or host name:

+|- host * | pattern

Allows (+) or denies (-) access to hosts matching the pattern. If host is an asterisk (*), the access permission serves as the default for all hosts.

If pattern consists only of numbers, it is considered an IP address pattern; otherwise, it is considered a host or domain name pattern. For IP addresses, the permission will be applied to any host whose IP address begins with pattern. For host or domain names, the permission will be applied to any host whose fully qualified domain name (FQDN) ends with pattern.

+|- group * | group[ group]...

Allows (+) or denies (-) access to authenticated realm users who are members of one of the listed groups. If group is an asterisk (*), the access permission serves as the default for all groups.

+|- user * | user[ user]...

Allows (+) or denies (-) access to authenticated realm users. If user is an asterisk (*), the access permission serves as the default for all users.

realm realm_name

Defines the realm to use as the source for user name, password, and group information for this ACL. The realm_name must exist in the web site's realms.conf(4) file, or all user and group permissions will be ignored.

EXAMPLES

Example 1

Access control for the Sun WebServer GUI server administration is defined in the global /etc/http/access.conf file. The special URI /sws-administration defines ACLs for administration:

 url "/sws-administration" {
   realm               serverAdmin
   authentication_type basic

   + user  *
 }

Example 2

A web site ACL to restrict HTTP publishing to valid users:

url "/" {
   realm               publishing
   authentication_type basic

   method PUT DELETE {
      + user *
   }

}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

The global /etc/http/access.conf is used by the Sun WebServer GUI. The command-line utilities protect server-wide administrative access using a pseudo-URI ("/sws_administration"). Similarly, the site-wide administrative access is protected by the server pseudo-URI at site-specific access.conf.

Sun WebServer 2.1 Last Revised 22 February 1999

content.conf(4)

NAME

content.conf- Represents meta-data for directories, site preferences for languages, media and encoding types, and specifying variants for content.

SYNOPSIS

site_path/conf/content.conf

DESCRIPTION

The content definitions may be created by htcontent(1m).

For directories, you can set whether they can be browsed and also sets the format for directory listings. You can also create a list of default file names to search for in the directory.

For files, you can set preferences for HTTP 1.1 content negotiation. Preferences include character set, language, compression encoding, and media type.

You can set variant information for a Uniform Resource Identifier (URI). If a URI has a set of associated file variants, the server will select the most appropriate variant based on the client's preferences and the preference settings on each file variant.

Syntax

The following syntax rules apply to the content.conf file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored.
White space is ignored in directive definitions.
Some directives accept a list of values. Separate multiple values by white space. If more than one line is required to list all values, escape all but the last newline with a backslash (\) at the end of the line.
Directives of the type name = value require whitespace around the = symbol.
All directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, newlines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks. Directive blocks also use matched curly braces to contain a definition. The url{} blocks can be embedded inside other url{} blocks. Then the embedded url{} block inherits information from its parent block unless it explicitly redefines a directive, in which case the directives in the child block will override the directives in the parent.

Content settings take the following form:

url <URI> {
variant <variant_info> 
	preferences {
		directory_listing {fancy | simple | off}
		default_files
		media_type
		language
		encoding
		charset
	}
	[url <file_uri> {
		filename <variant_info>
		preferences {
				media_type
				language
				encoding
				charset
		}
	}]...
}

The syntax and definition of each directive is explained in the following Directives section.

Directives

The following keyword directives are valid in the content.conf file:

preferences preferences

Sets the server's content negotiation preferences for the specified URI. Preferences are listed in order of preference. Separate multiple preferences with a space. Valid preferences are:

charset charset [[charset...]]

Specifies the character set of the data. A character set refers to a method used with one or more tables to convert a sequence of octets into a sequence of characters. The default charset for variants is ISO-8859-1.

default_file filename [[filename...]]

Specifies in order of preference the default files Sun WebServer looks for in a directory. If no match is found in this list of file names, the directory contents are displayed. Multiple files must be separated by whitespace. A different set of default files can be named in any directory.

Use the null string, "", as the file name to indicate that there is no default file for the directory. If no file is named, the directory contents will always be listed.

directory_listing method

Sets the method for displaying the contents of a directory when there is no file matching one of the default file names. The listing type can be "fancy" to display each directory entry as a hyperlink with the file size, the last modified time, and an icon next to each entry to indicate the file type; or "simple" to display directory entries as plain text hyperlinks; or "off" to display no directory contents.

encoding encoding [[encoding...]]

Specifies the preferred encodings or the encoding type. Encoding refers only to methods of compression. For example, gzip or compress reveals which methods have been used to encode the file.

language language [[language...]]

Specifies in order of preference the preferred languages. Languages are specified in the standard two-letter format.

media media_type [[media_type...]]

Specifies the preferred types of media. Media type is in standard MIME type format.

variant_info variants

Sets the server's variants for resources. Separate multiple variants with a space. Valid variants are:

charset charset [[charset...]]: Specifies the character set of the data. A character set refers to a method used with one or more tables to convert a sequence of octets into a sequence of characters.
encoding encoding [[encoding...]]: Specifies the preferred encodings or the encoding type. Encoding refers only to methods of compression. For example, gzip or compress reveals which methods have been used to encode the file.
language language [[language...]]: Specifies the preferred languages. Languages are specified in the standard two-letter format.
media_type media_type [[media_type...]]: Specifies the preferred types of media. Media type is in standard MIME type format.

EXAMPLES

Example 1

To add an encoded French variant and a German variant for the URI index.html:

url /index.html {
	   index.fr.html lang = fr enc = gzip char = iso-8809-1 type = text/html
	   index.de.html lang = de type = text/html; level=3.0
}

Note that the level=3.0 is part of the type definition; it indicates the HTML version level of the resource. If a browser uses the level in a request for an HTML document, and all other things are equal, the server will send the matching resource with the greatest HTML level acceptable to the client.

Example 2

To set the default files in a directory to index.html or index.shtml:

url /pages/ {

   preferences {
      directory_listing off
      default_files index.html index.shtml
   }

   url index.html {
      index.ja.html lang = ja char = EUC_JP
      index.en.html lang = en char = iso-8809-1
      index.fr.html lang = fr char = iso-8809-1
   }

}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

groups(4)

NAME

HTPASSWD

SYNOPSIS

site_path/conf/realms/HTPASSWD_realm/groups

DESCRIPTION

The groups file defines the groups in an HTPASSWD realm.

You may create new groups in the realm by htrealm(1m) or by the GUI.

All members of a group must be valid users defined in users(4).

Syntax

The following syntax rules apply to the groups file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored
White space is ignored in directive definitions.
This directive accepts a list of values. Separate multiple users by white space. If more than one line is required to list all values, escape all but the last new line with a backslash (\) at the end of the line.
Directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, newlines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks which also use matched curly braces to contain a definition.

Each group definition lists the member's user name separated by white space in the following form:

groupname {
	username1
	username2
}

EXTENDED DESCRIPTION

EXAMPLES

Example 1

Sample groups file:

# the groups file containing groups in an HTPASSWD realm
group administration {
	webmaster # group block listing members of the group
}
group group_two {
	user1
	user2
	user3
}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

Sun WebServer 2.1 Last Revised 22 February 1999

httpd-instances.conf(4)

NAME

^TM

SYNOPSIS

/etc/http/httpd-instances.conf

DESCRIPTION

The httpd-instances.conf file associates each unique httpd process (or server instance) with its configuration file, and defines whether or not a server instance is enabled. A server instance is a named httpd process that services one or more web sites. At installation, there are two default instances: sws_server and admin, the server process which handles the Sun WebServer GUI. The admin instance is not created unless SUNWhtadm has been installed.

Entries in httpd-instances.conf may be modified by using the htserver utility, through the Sun WebServer GUI, or editing the file directly. It is recommended that you use htserver or the Sun^TM WebServer^TM GUI.

A new server instance is typically needed only when it is impractical to add web sites to an existing server, either because all existing instances already have large numbers of sites or because a new web site requires a configuration that no existing instance can support. Instances cannot share port numbers.

Syntax

The following syntax rules apply to the httpd-instances.conf file:

The exclamation mark (!) is a comment character. All characters from a ! to the end of a line are ignored
White space is ignored in directive definitions.
Separate multiple values by white space or tab character.
Each entry is written on one line with three fields. Additional fields on the same line are ignored.
There is no syntax error checking for the first two fields (instance-ID and configuration_file). The third field can have any of the following values to indicate that the site is enabled: enabled, true, yes, 1. Any other value in this field would disable the site.

Each entry in httpd-instances.conf has the following format

<instance-ID> <configuration_file> <state>

The syntax and definition of each directive are explained in the following Directives section.

Directives

The following keyword directives are valid in the httpd-instances.conf file:

instance-ID

Shows the unique string used to identify the server instance. The instance-ID is used in the Sun WebServer GUI, command-line utilities, and (by default) to name the configuration file. The string may contain any alphanumeric characters, but may not contain spaces.

The instance-ID "admin" is reserved to name Sun WebServer. You should not delete or rename this server instance unless you want to disable web-based administration.

configuration_file

Shows the full path location of the configuration file for this server instance. By default, the configuration file will be /etc/http/instance-ID.httpd.conf, but any valid configuration file may be used.

state

Shows the state of the server for the purposes of starting all instances (such as when the machine boots). Valid values in this column are:

enable: Means the server will be started by default when the machine boots or when htserver start or htserver restart is run with no explicit instance name.
disable: Means the server will only be started if it is explicitly named. You must use htserver start instance-ID to start the instance.

EXAMPLES

Example 1

Do not edit the /etc/http/httpd-instances.conf file. This example is shown for reference only:

Secure_Sites    /etc/http/secure.httpd.conf     disable
Small_Sites     /etc/http/small.httpd.conf      disable
Large_Sites     /etc/http/sws_server.httpd.conf enable
admin   /usr/http/admin_server/conf/admin.httpd.conf   disable

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttp
Interface Stability	Evolving

NOTES

Do not edit httpd-instances.conf manually. Use htserver(1m) to add, delete, or modify instances.

Sun WebServer 2.1 Last Revised 22 February 1999

httpd.conf(4)

NAME

httpd.conf- Server instance configuration file.

SYNOPSIS

/etc/http/instance-ID.httpd.conf

DESCRIPTION

The server instance configuration file contains directives that define the server's runtime behavior, the web sites it hosts, and the network connection end points it uses.

The directives are grouped in three major divisions. The valid directives for each division are explained in separate sections below. The major divisions are:

server { }: Defines the behavior of the server process. Includes cache settings, the user ID of the server process, servlet engine settings, and server-wide defaults for the web sites hosted by the instance.
url hostname { }: Defines the identity and server resources used by a web site hosted by the server instance. There is one url {} block for each web site (or virtual host) handled by the instance, and it defines properties such as the web site's canonical host name and aliases, the location of the configuration file, and the network connections available to the web site.
port number { }: Defines the settings for a network connection or connections. The server process will attempt to bind to each port on each IP address defined in its port {} blocks. If a port is in use, the server will log an error. The server will exit if it cannot bind to at least one port. Port directives include the IP addresses on which to use the port and the timeout period.

Syntax

The following syntax rules apply to the httpd.conf file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored
White space is ignored in directive definitions.
Some directives accept a list of values. Separate multiple values by white space. If more than one line is required to list all values, escape all but the last newline with a backslash (\) at the end of the line.
Any value may optionally be enclosed in double quotes (").
All directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, newlines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks that also use matched curly braces to contain a definition.

The overall format of the file is:

server { 
   <server directives>
}
url  {
   site_path <absolute_pathname>
   site_conf <filename>
   <web site directives>
}
[ url <hostname> { <web site directives> } ]...
port <number> {
   <port directives>
}
[ port <number> { <port directives> } ]...

There must be only one server {} block. There must be at least one url {} block, and each block-except for the default site--must have a unique hostname, a site_path directory that exists, and a site_conf file that exists in the site_path. There must be at least one port {} block; duplicate port numbers are allowed as long as the IP address definitions are different.

See the "Extended Description" for the syntax of all valid directives in each division.

EXTENDED DESCRIPTION

`server {}` Block Directives

access_enable yes | no

Enables or disables the use of access control lists (ACLs) to control access to resources on the server. The default is yes.

cache_enable yes | no

Enables or disables server-side caching of documents. The default is yes. Caching can improve the performance by avoiding file system accesses for frequently requested static documents. Dynamic content, such as CGI output, is not cached.

cache_large_file_cache_size MB

Sets the size in MB of the server-side cache for large files. The large file cache caches files larger than 16 KB. The largest file size cached can be set with cache_max_file_size. The default value is 256 MB, and the maximum is only limited by virtual address space of the Sun^TM WebServer^TM process. You should rarely need to adjust this parameter.

cache_max_file_size MB

Sets the size of the largest file that will be cached in the large file cache. Documents that are larger than cache_max_file_size will never be cached. Caching works best by serving a large number of frequently requested documents. If the cache is filled with only a few very large documents, caching performance will be poor. The default cache_max_file_size is 1 (MB).

cache_small_file_cache_size MB

Sets the size in MB of the server-side cache for small files. The small file cache contains only documents smaller than 16 KB. Larger documents are stored in the large file cache or not cached at all. The default cache_small_file_cache_size is 8 (MB).

cache_verification_time seconds

Sets the number of seconds the server will wait before verifying the validity of a cached file. When Sun WebServer retrieves a file from the cache, if it has not been verified in cache_verification_time seconds, it is re-verified with the file on disk. If the dates are different, the file is removed from the cache and the actual file is retrieved. Cached files may be out of date if the actual file has changed. If your files only rarely change, you may want a higher value for cache_verification_time for improved performance. The default is 10 (seconds).

cgi_error_log_cycle_time [[days,]hours:]minutes

Sets the maximum age for CGI error log files. If a CGI error log is older than the number of cgi_error_log_cycle_time minutes, then a new request log file is started with an incremented sequence number. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. The log cycle time can be specified in days, hours, or minutes. For example, a log cycle time of 24 hours can be 1,0:0 (1 day), 24:0 (24 hours), or 1440 (1440 minutes). Default is 1 day.

cgi_error_log_enable yes | no

Enables or disables CGI script error logging. The default is no.

cgi_error_log_max_files integer

Sets the maximum number of CGI error log files that Sun WebServer will keep for this host. Log files end with a sequence number suffix which is incremented when a new log file is created. If the sequence goes beyond cgi_error_log_max_files, it is reset to 1 and the first CGI error log file is overwritten. This prevents the number of log files from growing without limit. Set cgi_error_log_max_files to "-1" to have no limit on the number of log files. Default is 7 files.

cgi_error_log_max_file_size bytes

Sets the maximum file size, in bytes, for CGI error log files for the current host. If a CGI error log exceeds cgi_error_log_max_file_size, a new log file is started with an incremented sequence number. Default is 1048576 bytes (1 MB).

cgi_error_log_prefix prefix

Sets the directory and log file name prefix for CGI script error logs for a given server. The string can have either an absolute or a relative path name followed by the prefix that will be used for this server's log files. Separate servers must have different prefix names so that there is no conflict in writing to the logs. Each server's log files will have a name in the form:

<pathname>/prefix.<sequence>

For example, <server_root>/logs/error_log.2. Sequence is incremented and a new file created whenever cgi_error_log_cycle_time or cgi_error_log_max_file_size is reached. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. Default is "logs/error_log".

comment "description"

Simply a comment string to describe the current configuration file.

cookie_enable yes | no

Specifies whether the server sends cookies to the client. A cookie is an HTTP header that consists of a text-only string that gets entered into the memory of the client's browser. Session IDs are carried by the cookies in servlet sessions. Default is "yes".

default_file file [[file...]]

Lists in order of preference the name of the file Sun WebServer will look for in a directory when a URL request does not name a specific file. For example, if the URL request is for http://hostname/, Sun WebServer will look at the top directory of the host name's doc_root for the file specified as the default_file.

If default_file does not appear in the configuration file, then "index.html" is used. If default_file is set to an empty string (""), then no default file is used. If multiple files are specified, then the files are used in the specified order.

If no file matching the values for default_file is found, the directory contents will be listed, subject to the value of directory_listing.

The built in server-wide default is "index.html".

directory_listing fancy | simple | off

Specifies how the contents of directories will be listed if no file matching default_file is found in the directory. directory_listing is valid in server {} blocks as server-wide defaults or in url {} blocks for per-host settings.

fancy: Displays directory contents with each name as a hyperlink to the file, icons matching each file's type, and file size and date information. The icons used and the association of icons to file suffixes is configurable.
simple: Displays only each file name as a hyperlink to the file itself.
off: Disables displaying directory contents; an HTTP "404 Not Found" error is returned to the client instead.

The built in server-wide default is "fancy".

error_document http_error_code_url

Allows customized error messages to be returned to the client. Any valid URL, including CGI scripts, may be returned, so you have flexibility in what information you want to give clients when an error occurs. When an HTTP error code is returned, Sun WebServer will return an HTTP "302: Document Moved" status with a Location: header indicating the file to which the error has been remapped. Most clients will automatically fetch the URL named by the Location: header. You can redirect the following HTTP error codes:

400 - Bad Request (Remapped by default host only)
403 - Forbidden
404 - Not Found
412 - Precondition Failed
500 - Server Error
501 - Not Implemented
503 - Service Unavailable

The destination URL can be relative to the current or default host if it begins with a "/". Otherwise, an absolute URL must be specified. The following examples show a relative and absolute URL, respectively:

error_document 503 "/cgi-bin/error.pl?503"
error_document 500 "http://www2.A.com/mirror/"

Note -

The path to which you remap 404 errors must be available in the document root. You can not redirect 404 errors to aliased directories. error_document is valid in server {} blocks as server-wide defaults or in url {} blocks for per-host settings.

icon_add alt_text bitmap_URI file_type[[file_type]]...

Allows association of a file extension with an icon file. The icon will be used to represent all files with the extension in fancy directory listings. icon_add can also change a default association or assign icons to file types not covered in the default set; for example, you may want to use your own icons to represent basic types. In addition to file suffixes, you can customize the icon used for "parent directory" (../) and "subdirectory" by specifying "UP" or "DIR" as the alt_text.

alt_text: Specifies a string that will be used instead of an icon in text-only browsers. For example, "GIF".
bitmap_URI: Specifies a URI path relative to the default host (in the server {} block) or the host named by the current url {} block. For example, "/icons/binary.xbm".
file_suffix(es) | content_type(s): Specifies a string of one or more file extensions or content type definitions that will use the icon in "fancy" directory listings.

In addition to file suffixes, you can customize the icon used for "parent directory" (../) and "subdirectory" by specifying "UP" or "DIR" as the alt text. icon_add is valid in server {} blocks as server-wide defaults or in the site configuration files for per-host settings.

For example,

icon_add "IMG" "/sws-icons/image.xbm" "gif jpeg xbm"

displays the icon in "/sws-icons/image.xmb" for "gif" "jpeg" and "xbm" files . In text-only browsers, the text "IMG" is displayed.

icon_default bitmap_URI

Sets the icon used for files with extensions that do not have a defined icon type. The path to the bitmap file must begin with a "/", and it is relative to the default host or the host defined by the current url {} block. icon_default is valid in server {} blocks as server-wide defaults or the site configuration files for site-level settings.

lwp_threads_count integer

Sets the total number of lightweight process (LWPs) threads in the kernel that Sun WebServer will attempt to use to map to user threads in its thread pool. By default, Sun WebServer uses 1 LWP per user thread (lwp_threads_count will equal threads_n_active).

Increasing this number may increase the actual thread concurrency of Sun WebServer, and it will also increase the share of system resources used by the httpd process.

mime_file relative_path

Contains the default MIME types definitions used for the server host. Default is /etc/http/mime.types.

If no MIME type for the file can be found, the mime_default_type is used. Entries in the mime_file have the form:

<media type>/<media subtype> <file suffix(es)>

For example: text/html html htm. The default server-wide mime_file is /etc/http/mime.types.

mime_default_type type/subtype

Sets the MIME type that will be used for files whose extension does not match any other MIME type. The default is "text/html". mime_default_type is valid in server{} blocks as server-wide defaults or in the site configuration files for per-host settings.

se_session_enable yes | no

Specifies whether sessions are supported for all servlet engines. A session is a series of requests from the same user that occur during a time period. If set to "no", servlet engines do not extract or insert session information into requests and no session swapping will be performed. If set to "yes", session information will be extracted and inserted as necessary, and session swapping is also performed when necessary. Default is "yes".

se_session_persistence yes | no

Specifies whether the server should keep session data persistent. If set to "yes", serializable data in sessions are swapped to disk before the server shuts down and revalidated from disk when the server restarts. If set to "no", the server removes swapped sessions each time it starts. Default is "yes".

server_admin email_address

Specifies the email address of the Sun WebServer administrator.

server_classpath path[[:path]]...

Specifies the Java^TM classpath where the JDK, JSDK, and classes for the servlet engine are located. This is not the path for servlets to be loaded.

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_classpath, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_java_initial_heap_size bytes

Specifies how much memory is allocated for the heap when the Java virtual machine (JVM) starts. This directive has the same fuctionality as the command-line option -ms in Java. Default is 1048576 bytes ( 1MB ).

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_java_initial_heap_size, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_java_max_java_heap_size bytes

Specifies the maximum heap size for the interpreter. This directive has the same fuctionality as the command-line option -mx in Java. Default is 16777216 (16MB).

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_java_max_java_heap_size, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_java_max_stack_size bytes

Specifies the maximum stack size for Java code for each Java thread. This directive has the same fuctionality as the command-line option -oss in Java. Default is 409600 bytes (400KB).

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_java_max_stack_size, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_java_max_native_stack_size bytes

Sets the maximum stack size for native code for each Java thread. This directive has the same fuctionality as the command-line option -ss in Java. Default is 131072 bytes (128KB).

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_java_max_native_stack_size, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_java_properties key=val [[key=val]]...

Specifies new properties for the system properties list in Java. This directive has the same fuctionality as the command-line option -D in Java.

Note -

Because running the command-line utility htserver restart or restarting the server from the Sun WebServer GUI does not restart the Java virtual machine, if you change server_java_properties, you must kill and restart the Sun WebServer process in order for your changes to take effect.

server_root absolute_path

Specifies the path in which the server-wide scripts, icons, and base for sites hosted by the instance are stored. CGI and servlet error log file prefixes are relative to server_root when the log prefixes are specified without a leading "/".

server_user username

Sets the user name Sun WebServer will use after start up. The string must be a valid user name on the system. After httpd is started by root, it will change to the server_user user name. The default server_user is root. The server_user must be able to read and write the configuration file, any ACL files, read files in the doc_root directories, and be able to read and write files in any log file directories. You can set the server_user so the server does not run with root permissions. By running as a different user, there are fewer security risks because the server will be unable to change or serve to the clients sensitive files owned by root. You may want to create a user only to run Sun WebServer, and make sure that this user owns or has access to all of the necessary files and directories.

servlet_engine { parameters }

Specifies parameters of the servlet engine:

chaining_enable yes | no

Enables or disables servlet chaining. This enables the servlet engine to run a sequence of servlets in a specified order to fulfill one single servlet request. Host administrators can specify a chain of servlets to be executed sequentially. Default is "no".

cookie_comment comment

Specifies the value of the comment field in cookies with session IDs. Default is "Sun Web Server Session Tracking Cookie".

cookie_domain domain

Specifies the domain where cookies with session IDs are valid. For example, if a cookie has a domain of "www.A.com", then only "www.A.com" will recognize it as a valid cookie. All other servers will reject this cookie.

cookie_max_age seconds

Specifies the value of the max-age field sent for cookies with session IDs. A cookie with cookie_max_age 0 expires immediately.

cookie_name name

Specifies the name of a cookie used to carry the session ID when cookies are enabled. Default is "swssessionid".

cookie_path path

Specifies the value of the path field sent for cookies with session IDs. This allows you to set the URL path where the cookie is valid. Pages outside of this path cannot read the cookie. This path is relative to doc_root. Default is "/".

cookie_secure yes | no

Specifies the value of the secure field sent for cookies with session IDs. This directive indicates whether a cookie should only be used under a secure server condition, such as SSL. Default is "no".

dynamic_linking_enable all | local | remote | none

Allows the specified servlets access to dynamic libraries. Default is "none".

file_access_enable all | local | remote | none relative_path

Allows specified servlets to have access to file resources, for example, read/write a file on local disk. Default is "local".

network_access_enable all | local | remote | none

Allows specified servlets to have access to network resources, for example, open a socket. Default is "local".

properties_file path

Path to the "servlets.properties" file. All loadable servlets are specified in this file. Each servlet engine instance can have a list of preloaded servlets that it wishes to load and initialize as soon as the server starts. This list is specified in a servlet properties file. Path can be either absolute or relative to server_root. Default is "conf/servlets.properties".

reload_enable yes | no

Allows or disallows the servlets to reload. If the servlet classfile changes, a servlet instance (reflecting the changes) can be reloaded. Reloading can be performed by either the server or the host administrator, depending on whether the hosts are sharing a servlet engine instance. Servlets do not reload automatically and will reload only when explicitly requested. Default is "no".

remote_enable yes | no

Enables or disables remote servlets. Enabling remote servlets allows the servlets from remote sites to be loaded by the server. The default is "yes".

se_log_enable yes | no

Enables or disables the servlet error logging. The default is "no".

se_log_cycle_time [[days,]hours:]minutes

Sets the maximum age for servlet error log files for the current host. If a servlet error log is older than the number of se_log_cycle_time minutes, then a new servlet error log file is started with an incremented sequence number. If a log file contains no entries, then no new log file will be generated, regardless of how much time has passed. The log cycle time can be specified in days, hours, or minutes. For example, a log cycle time of 24 hours can be 1,0:0 (1 day), 24:0 (24 hours), or 1440 (1440 minutes). Default is 1 day.

se_log_max_files integer

Sets the maximum number of servlet error log files that Sun WebServer will keep for this host. Log files end with a sequence number suffix which is incremented when a new log file is created. If the sequence goes beyond se_log_max_files, it is reset to 1 and the first servlet error log file is overwritten. This prevents the number of log files from growing without limit. Set se_log_max_files to "-1" to have no limit on the number of log files. Default is 7 files.

se_log_max_file_size bytes

Sets the maximum file size, in bytes, for servlet error log files for the current host. If a servlet error log exceeds se_log_max_size, a new log file is started with an incremented sequence number. Default is 1048576 bytes (1 MB).

se_log_prefix absolute_path/prefix

Sets the directory and log file name prefix for servlet error logs for a given servlet engine. The string can have either an absolute or a relative path name followed by the prefix that will be used for this servlet engine's servlet log files. Separate servlet engines must have different prefix names so that there is no conflict in writing to the logs. Each servlet engine's servlet log files will have a name in the form:

<pathname>/prefix.<sequence>

For example, <server_root>/logs/se_log.2. Sequence is incremented and a new file created whenever se_log_cycle_time or se_log_max_file_size is reached. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. Default is"logs/se_log".

security_access_enable all | local | remote | none absolute_path/prefix

Allows the specified servlets to have access to security resources, for example, classLoaders. Default is "local".

send_auth_hdrs yes | no

Specifies whether to send authorization headers to servlets. Authorization headers hold information about client authentication such as encoded user name and password. Default is "no".

session_invalidation_time [[days,]hours:]minutes

Specifies the length of time that a sesssion is allowed to remain unused before it is invalidated and denied further access. Default is 30 minutes.

session_max_residents integer

Specifies the number of sessions allowed to remain in memory. If the number of sessions exceeds this number, then sessions are swapped out to disk (beginning with the least-recently used session) to reduce the number of resident sessions. Default is 4096.

session_protocol_switch_rewriting yes | no

Specifies whether session ID is added to URLs when URL dictates a switch from "http" to "https" or vice-versa. Used only in servlet URL rewriting. Default is "no".

session_swap_directory path

Specifies the directory path where the swapped sessions reside. The path can be either absolute or relative to server_root.

singlethreadmodel_init_pool_size integer

Specifies the initial number of instances of a single servlet to be spawned in the case of SingleThreadModel servlets. Default is 5.

singlethreadmodel_max_pool_size integer

Specifies the maximum number of instances of a single servlet to be spawned in the case of SingleThreadModel servlets. Default is 20.

system_access_enable all | local | remote | none

Allows or disallows the specified servlets to have access to system resources, for example, call System.Exec(). Default is "local".

servlets_path path

Specifies the absolute path to local directories and JAR files for all local servlets. This is a colon-separated list.

server_servlets_enable yes | no

Allows or disallows servlets to run in this server process. This option controls whether to start the JVM for this process. The default is "no".

site_restrictions { directives }

Enables access to the following:

cgi_superuser yes | no

Allows or disallows cgi_user setting of any web site to be root. Default is "no".

cgi_user_unique yes | no

Determines whether the cgi_user setting of any web site must be unique throughout the server. Default is "yes".

cgi_dns_enable yes | no

Enables or disables the REMOTE_HOST CGI environment variable to be set and to be available to CGI scripts. REMOTE_HOST requires a DNS lookup of the IP address (REMOTE_ADDR) of the resource making the CGI request. Since DNS lookups can be resource consuming, allowing such DNS lookups can slow performance, especially on a server that uses extensive CGI. If you use getRemoteHost() or getRemoteAddr() or similar calls in your servlet programs requiring name resolution, cgi_dns_enable must be set to "yes" on both the server and the web site level. If you change this directive, you must restart the server in order for your change to take effect. The default is "no".

se_share yes | no

Enables all web sites to share the servlet engine defined in the server block if set to "yes".

If set to "no", there is no sharing and each web site can have its own servlet engine. This is a server-wide setting. The default is "no".

symlink_follow yes | no

Follows or ignores symbolic links in the file system. Ignoring symbolic links may cause a performance loss as the file name and each directory in the path of a requested resource must be checked to make sure there are no symbolic links. Following symbolic links may be a security risk because a symbolic link can potentially point to a file that is outside of the doc_root. A symbolic link to a sensitive file (such as /etc/passwd) can only be made by someone with write access to the file, so the security risk is often small and easily managed by controlling who has access to the document root. symlink_follow is valid in server {} blocks as server-wide defaults or in the site configuration files for per-host settings. Default is "yes".

threads_n_active integer

Specifies the maximum number of user threads Sun WebServer will have available in its thread pool. The number of threads will not grow beyond this number. Sun WebServer uses one thread per connection, releasing the thread to the thread pool when the request has completed. For keepalive connections, the thread is released to the thread pool after a request has completed, and a new thread is used if there is a new request on the connection. The number of threads sets an upper limit on the number of simultaneous connections Sun WebServer can handle. The default value is 128 threads.

url_rewriting_enable yes | no

Specifies whether the server uses rewritten URLs as a vehicle to carry the session ID of a servlet session. Rewritten URLs are URLs with session IDs embedded in them. The server also recognizes session IDs in the incoming URLs. Default is "no".

user_doc_source UNIXSYS | ISP

Specifies the source of user information for user document directories if user_doc_enable is "yes." In most cases, the only valid value is UNIXSYS, and users are defined through the operating system (for example, in /etc/passwd or NIS).

In the Solaris^TM ISP Server^TM software, if virtual FTP servers have been defined in Sun Directory Services, you may set this to ISP. User information will be taken from the directory server, and the value of a user's ispContentDirectory will be used.

version version_string

Describes the current version of Sun WebServer.

`url {}` Block Directives

alias hostname

Defines other names for the specified virtual host.

conn_end_points [[ip_address | *]]:port [[[[ip_address | *]]:port]]...

Determines the IP address and port numbers on which requests to this web site are accepted. The syntax of this directive is

[<ip_address>]:port number

If the ip_address refers to the set of all IP addresses for this web site, then for HTTP 1.1 virtual hosts, leaving the ip_address field blank means that it is available on all IP addresses.

This directive may not appear in the url {} block for the default virtual host. In consequence, the default host will receive all requests to unknown hosts and all HTTP 1.0 requests not addressed to any host that arrives on any port. The server rejects with error 400 HTTP 1.1 requests not addressed to any host.

owner_group groupname

Defines the UNIX group who owns the web site's content files.

owner_user username

Defines the UNIX user and group who own the web site's content files.

site_config path

Specifies the relative path to a web site's configuration files.

site_enable yes | no

Determines whether the site is currently enabled and accepting requests. site_enable is not an initialized setting. A site is enabled once it has been configured successfully. After successful configuration, use hthost to enable or disable the site.

site_path directory_path

Specifies the absolute path location of the web site.

`port {}` Block Directives

expected_load low | medium | high

Specifies the anticipated level of request traffic on this port. Setting this directive to "low" indicates that the number of incoming requests on this port is expected to be low, so Sun WebServer dedicates fewer resources to handle the requests on this port. If set to "high", that the number of incoming requests on this port is expected to be high, so Sun WebServer allocates more resources to handle the requests on this port. The "medium" setting is appropriate for most situations. However, setting ports with high traffic (hundreds of requests per second) to "high" will improve the throughput of Sun WebServer, and setting ports with little traffic to "low" will improve overall resource allocation in Sun WebServer. The default is "medium".

ip_address nnn.nnn.nnn.nnn

Indicates the IP address on the server that can receive requests on the current port. Use this if you do not wish to support all IP addresses on a port. You need to create a separate port {} block with the same port number for each specific ip_address you want to support. Use separate port {} blocks with unique ip_address settings to support IP-based virtual hosting. If this parameter is omitted, all IP addresses on the server will be supported on the port. The default is all IP addresses.

keepalive_enable yes | no

Allows or disables HTTP 1.0 keepalive connections on the current port. HTTP 1.1 connections always use keepalive, but HTTP 1.0 browsers can only establish a keepalive connection with Sun WebServer by sending a Connection: keepalive HTTP header (if keepalive_enable is set). Keepalive may improve performance since the connection is not destroyed and reestablished for each HTTP request. The default is "yes".

request_timeout seconds

Sets the maximum time, in seconds, that Sun WebServer will wait to fill an individual client request on the current port. The default is 180 seconds (three minutes).

ssl_client_cert_required yes | no

Determines whether the server will demand a certificate signed by a Certificate Authority (CA) known to the server when a client connects to the SSL port. The default is "no".

ssl_enabled yes | no

Enables or disables the Secure Sockets Layer (SSL). SSL encrypts and authenticates messages sent between a browser and Sun WebServer. Encryption using public key cryptography ensures the privacy of the messages sent between the client and Sun WebServer. Port 443 is the default SSL port and is recommended for easiest use by clients (no port will need to be specified in the https URL). The default is "no".

Note -

To run SSL, you will need to set up a local root Certificate Authority (CA) with a Distinguished Name record, and generate a private/public key pair for the local root CA. The local root CA will be able to generate credentials and key pairs for every SSL-enabled host within your organization, whether it is a single host or a machine running Sun WebServer with hundreds of virtual hosts. The security tools use the Federated Naming System (FNS) to manage the naming context for users and hosts with certificates.

ssl_ciphers cipher_string(s)

Sets the cipher parameters used for SSL encryption. It may be one of the following:

Note -

For domestic software, to ensure successful operation with various browsers, always include the strongest available cipher choice (SSL_RSA_WITH_RC4_128_MD5) in the ssl_ciphers attribute when you enable SSL on a port.

SSL_RSA_EXPORT_WITH_RC4_40_MD5: For 40-bit exportable ciphers. This is the default setting.
SSL_RSA_WITH_RC4_128_MD5: For 128-bit, North America only cipher (this requires separate SSL packages not available in the downloadable version of Sun WebServer).

EXAMPLES

Example 1

A sample configuration file:

# Automatically generated.
#
#       SWS HTTP server configuration file
#
# file version number
version "SWS2.1"
server {
        comment                  "Sample Configuration"
        server_root              "/var/http/sample/"
        server_user              "root"
        cache_enable             "yes"
        cache_large_file_cache_size 256
        cache_max_file_size      1
        cache_small_file_cache_size 8
        cache_verification_time  10
        cgi_error_log_cycle_time 1,0:0
        cgi_error_log_enable     "no"
        cgi_error_log_max_files  7
        cgi_error_log_max_file_size 1048576
        cgi_error_log_prefix     "error_log"
        cookie_enable            "yes"
        lwp_threads_count        1
        threads_n_active         128
        access_enable            "yes"
        symlink_follow           "yes"
        user_doc_source          "ISP"
        directory_listing        "fancy"
        default_file             index.html
        mime_default_type        "text/html"
        mime_file                "/etc/http/mime.types"
        icon_default             "/sws-icons/unknown.xbm"
        
        site_restrictions {
                se_share                 "no"
                cgi_superuser            "no"
                cgi_user_unique          "no"
                cgi_dns_enable           "no"
        }
        server_classpath         "/usr/lib/http/classes.zip:\\
							/usr/jsdk/lib/classes.zip:/usr/java/lib/classes.zip"
        server_servlets_enable   "yes"
        se_session_enable        "yes"
        se_session_persistence   "yes"
        url_rewriting_enable      "yes"
}
url {
        site_enable              "yes"
        site_path                "/var/http/sample/websites/default_sites"
        site_config              "conf/default_sites.site.conf"
        owner_user               "admin3"
}
port 80 {
        ip_address           129.146.146.146
        keepalive_enable         "yes"
        request_timeout          180
}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

All configuration parameters are editable through the Sun WebServer GUI. For administrators who use the command-line utilities or do not have access to the Sun WebServer GUI (for example, if the administrator is remote and does not have access through a firewall), there are some directives that can not be changed using the command-line utilities. These directives must be manually edited in the configuration files. In this case, the changes made directly in the configuration files may conflict with the edits from the GUI and the command-line utilities.

All non-servlet related directives, all port{} block directives, web site alias directives (in host{} block), and the conn_end_points directive (in host{} block) are not explicitly supported in the command-line utilities. If they are modified through an editor, then the synchronization of file writes are handled through UNIX (outside of the file locking mechanism used by both the administration and the command-line utilities). This could lead to file inconsistencies not encountered if one performed management exclusively through the Sun WebServer GUI.

When the CGI and servlet logs are enabled, they capture output from the standard error streams of CGI scripts and servlets in cycled log file sets that Sun WebServer manages. Enabling these logs can impair Sun WebServer's throughput because scripts and servlets often use the log files for debugging messages which can flood the log files; this file system traffic can degrade performance on a heavily loaded web site. However, to debug CGI scripts and servlets, or to record all the CGI and servlet output, you must enable the error log. You can minimize the disk space requirements by carefully choosing the cycling parameters from the server configuration screens in the Sun WebServer GUI.

Sun WebServer 2.1 Last Revised 22 February 1999

httpd.event.logs(4)

NAME

httpd.event.logs- Description of the Events Log files.

SYNOPSIS

/var/adm/messages

DESCRIPTION

The httpd server puts out error messages and warnings via syslogd(1m) to /var/adm/messages by default. Use /etc/syslog.conf to change the default location.

Syntax

The definitions in the httpd.event.logs file have the following format:

<time> <host> sws.<instance>[pid]: [<version> <message_id> <seq_no> (<source>) <severity>]:  <message>

Errors sent to the screen before the daemon has been created or started are sent in console format. The format of the messages written to the console will be:

<message_id> <time> <severity>:  <message>

The following keyword directives are valid in the httpd.event.logs file:

time

The date and time (in the format: MM DD hh:mm:ss) that the error occurred.

host

The node name of the host (uname --n).

tag [pid]

A tag and a PID form the framework for error messages from user space. The tag reveals which Sun^TM WebServer^TM daemon logged the message. The instance name spans multiple starts and stops of a single server. The tag contains the instance name of the server preceded by "sws". The PID contains the process ID of the process that generated the error message.

version

The version of the error message format.

message_id

The unique identifier for the error message with the form modulename.id_number. The modulename refers to a shared object or to a subsystem in the httpd daemon code. The id_number mirrors the message catalog number.

seq_no

A sequence number determines the exact sequence of error messages in the log. This field is always "0" for Sun WebServer.

source

This field contains the source of the error. The source is always "SW" for Sun WebServer.

severity

The errors can be one of four severity levels:

CRITICAL: Critical condition such as failure to daemonize.
ERROR: Error conditions such as server being unable to bind to port. Error conditions cause a significant part of the server to fail.
WARNING: Warning conditions such as being unable to write to a log file. Warning conditions do not prevent the server from running.
NOTICE: Normal but significant conditions. These may require special handling.

message

The actual text of the message.

EXAMPLES

Example 1

Sample event log entries:

May 17 15:39:10 hostname sws.admin[14454]: [1 httpd.134 0 (SW) NOTICE]: \\
Received a SIGHUP signal; restarting the server.

May 17 15:39:10 hostname sws.admin[14454]: [1 admin.195 0 (SW) NOTICE]: \\
Running with SWS Configuration file \\
"/usr/http/admin_server/conf/admin.httpd.conf".

May 18 15:35:33 hostname sws.Secure_Sites[15257]: [1 net.61 0 (SW) WARNING]: \\
Network interface 129.146.146.25 is not configured on this host.

May 18 15:35:33 hostname sws.Secure_Sites[15257]: [1 net.183 0 (SW) ERR]: \\
httpd cannot bind to any configured port

May 18 15:36:49 hostname sws.Large_Sites[15077]: \\
[1 servlet.231 0 (SW) WARNING]: Servlets not allowed in this server.\\
 The specified servlet-engine block in virtual host www.A.com will be ignored

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttp
Interface Stability	Evolving

NOTES

To ensure that all Sun WebServer messages are logged by syslogd(1m), create an entry for daemon.notice messages in syslog.conf(4).

For example, to log Sun WebServer messages to /var/adm/messages, create the following entry:

daemon.notice			/var/adm/messages

Note -

The white space between the message type and the file name consists only of tabs.

This entry would cause all messages with a severity of "notice" or greater generated by any daemon process to be logged to /var/adm/messages.

Sun WebServer 2.1 Last Revised 22 February 1999

httpd.request.logs(4)

NAME

^TM

SYNOPSIS

site_path/log-prefix

DESCRIPTION

The httpd.request.logs file logs all incoming requests to a server request log file. Sun WebServer generates log files using one of three log file formats configurable by the administrator: the Common Log Format (CLF), the Extended Common Log Format (ECLF) also known as the Combined Log Format, or the Extended Log Format (ELF). The location of a request log file is set by the log-prefix directive in the site_path/conf/httpd.site.conf or in the Sun WebServer GUI.

The most recent log file can be accessed through the log prefix. If the default prefix http_log located at site_path/http_log has the ELF log type, then apart from having log files with names /site_path/http_log.elf.1, you will also have a symbolic link called site_path/http_log.elf, which points to the latest log file that the server is writing.

Note -

If you are running on the Solaris ISP Server^TM software and you are also running the network cache accelerator (NCA), check the NCA log file (specified with the logd_path_name directive in /etc/ncalog.conf) for additional log entries. Sun WebServer does not record all requests in the site request log on ports where NCA is running. Also, note that cache misses may be logged in both the Sun WebServer site request log as well as the NCA log, and some events such as requests for the site on ports not running NCA may be logged only in the Sun WebServer site request log.

Common Log Format (CLF)

The CLF format is used by most HTTP servers and analysis tools.

To get CLF logs, set log_type to "clf" in the web site configuration file.

The entries in the Common Log File (CLF) logs have the following format:

host rfc931 authuser [DD/MM/YYYY:hh:mm:ss] "request" ddd bbbb

The following list explains the log entry fields::

host: The DNS name or the IP number of the remote client.
rfc931: The information returned on this client for this request, otherwise (-).
authuser: The user ID sent for authentication, otherwise (-).
DD/MM/YYYY:hh:mm:ss: The date and time of the request.
request: The first line of the HTTP request as sent by the client.
ddd: The HTTP status code returned by the server, if not available (-).
bbbb: The number of bytes sent, not including the HTTP header, if not available (-).

Extended Common Log Format (ECLF)

An extended common log format file is a variant of the common log format file with two additional fields at the end of the line, the referrer and the user agent fields.

To get ECLF logs, set log_type to "eclf" in the web site configuration file.

The entries in the ECLF log files have the following format:

<host> rfc931 authuser [DD/MM/YYYY:hh:mm:ss GMT_offset] \\
"request" ddd bbbb "referrer" "user_agent"

The following list explains the log entry fields:

host: The DNS name or the IP number of the remote client.
rfc931: The information returned on this client by identd for this request, otherwise (-).
authuser: The user ID sent for authentication, otherwise "-".
DD/MM/YYYY:hh:mm:ss: The date and time of the request.
GMT_offset: The difference between the local time and Greenwich Mean Time (GMT).
request: The first line of the HTTP request as sent by the client.
ddd: The status code returned by the server, if not available (-).
bbbb: The number of bytes sent, not including the HTTP header, if not available (-).
referrer: The URL the client was on before requesting your URL, if not available, (-).
useragent: The software the client claims to be using, if not available (-).

Extended Log Format (ELF)

The Extended Log File (ELF) format is a flexible format for recording HTTP requests, which is particularly suited for log analysis tools. ELF records more information than the CLF format. It contains a sequence of lines containing ASCII characters delimited by a new line. Lines that start with # are comment directives.

To get ELF logs, set log_type to "elf" in the web site configuration file.

The entries in the ELF log files have the following format:

date time cs-method cs-uri sc-status time-taken bytes cs-ip cs-host

The following list explains the log entry fields:

date: The date in YYYY-MM-DD format.
time: The time the request was accepted by the server in the 24-hour format in the machine's time zone.
cs-method: The client-to-server HTTP method.
cs-uri: The client-to-server requested URI.
sc-status: The server-to-client HTTP status code in the response.
time-taken: The time taken to process the request.
bytes: The number of bytes sent.
cs-ip: The client-to-server IP address and port of the client.
cs-host: The DNS name of the remote client, if not available "-".

EXAMPLES

Example 1

Extended log format (elf):

#Version: 1.0
#Software: Sun_WebServer/2.1
#Start-Date: 1998-05-18 17:57:20
#Fields: date time cs-method cs-uri sc-status time-taken bytes \\
cs-ip cs-host cs-referer cs-agent

1998-05-18 17:57:01 GET / 200 0 848 129.146.114.74:49028 -

1998-05-18 17:57:13 GET /swshelp/ht_helpTOC.doc.html \\
304 0 142 129.146.114.74:49028 -

1998-05-18 17:57:20 GET /swshelp/ht_server_cache_settings.html \\
304 0 142 129.146.114.74:49028 -

1998-05-18 17:57:21 GET /swshelp/frame.ht_server_cache_settings1.html \\
304 1 142 129.146.114.74:49032 -

1998-05-18 17:57:21 GET /swshelp/SWSbanner.gif \\
304 0 142 129.146.114.74:49032 -

Example 2

Common log format (clf):

129.146.114.74 - - [18/May/1998:17:47:58 -0700] \\
"GET /monhelp/SISP_Banner.html HTTP/1.0" 200 558

129.146.114.74 - - [18/May/1998:17:48:11 -0700] \\
"GET /swshelp/ht_server_cache_settings.html HTTP/1.0" 200 379

129.146.114.74 - - [18/May/1998:17:48:12 -0700] \\
"GET /swshelp/ht_server_cache_settings1.html HTTP/1.0" 200 2645

129.146.114.74 - - [18/May/1998:17:48:12 -0700] \\
"GET /swshelp/SWS_Banner.html HTTP/1.0" 200 330

129.146.114.74 - - [18/May/1998:17:48:25 -0700] \\
"GET /swshelp/ht_server_web_sites_list.html HTTP/1.0" 200 379

129.146.114.74 - - [18/May/1998:17:49:09 -0700] \\
"GET /mchelp/awsTOC.doc.html HTTP/1.0" 200 5953

129.146.114.74 - - [18/May/1998:17:48:12 -0700] \\
"GET /swshelp/SWSbanner.gif HTTP/1.0" 200 16712

Example 3

Extended common log format (eclf):

129.146.114.74 - - [18/May/1998:18:02:56 -0700] \\
"GET /swshelp/ht_server_web_sites_list.html HTTP/1.0" 304 142 \\
"http://isp-doc1/swshelp/ht_helpTOC.doc.html" \\
"Mozilla/4.02 [en] (X11; U; SunOS 5.6 sun4m)"

129.146.114.74 - - [18/May/1998:18:03:03 -0700] \\
"GET /swshelp/ht_server_iplist2.html HTTP/1.0" 200 2377 \\
"http://isp-doc1/swshelp/ht_helpTOC.doc.html" \\
"Mozilla/4.02 [en] (X11; U; SunOS 5.6 sun4m)"

129.146.114.74 - - [18/May/1998:18:03:05 -0700] \\
"GET /swshelp/ht_server_iplist3.html HTTP/1.0" 200 341 \\
"http://isp-doc1/swshelp/ht_helpTOC.doc.html" \\
"Mozilla/4.02 [en] (X11; U; SunOS 5.6 sun4m)"

129.146.114.74 - - [18/May/1998:18:03:02 -0700] \\
"GET /swshelp/frame.ht_server_iplist2.html HTTP/1.0" 200 249 \\
"http://isp-doc1/swshelp/ht_helpTOC.doc.html" \\
"Mozilla/4.02 [en] (X11; U; SunOS 5.6 sun4m)"

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttp
Interface Stability	Stable

httpd.servlet.logs(4)

NAME | DESCRIPTION | EXAMPLES | ATTRIBUTES | SEE ALSO

NAME

httpd.servlet.logs and httpd.cgi.logs- The log files for servlet requests and CGI script errors.

DESCRIPTION

The httpd.servlet.logs log errors are generated by servlets. You can specify the location of the log files with htservlet or through the Sun^TM WebServer^TM GUI. See htservlet(1m) for details on configuring log settings.

The httpd.cgi.logs log errors are generated by CGI scripts. You can specify the location of the log files through the Sun WebServer GUI.

Log files will be named prefix.sequence, where sequence is a cycling number. Each entry is a Common Log File (CLF) format header indicating the request that launched the servlet or CGI, followed by all error messages generated during the request.

The servlet error logs will have the following format:

{client_name  [DD/MM/YYYY:hh:mm:ss] "request" "vhostname" "script_file_name"} 
error_messages

error_messages

The CGI error logs will have the following format:

{client_name  [DD/MM/YYYY:hh:mm:ss] "request" "vhostname" "script_file_name" [block_number]} 
error_messages

error_messages

block_number

FINAL

The most recent log file can be accessed through the log prefix. If the prefix is /var/http/logs/se_log, then apart from having log files with names /var/http/logs/se_log.1, you will also have a symbolic link called /var/http/logs/se_log, which points to the latest log file that the server is writing.

See httpd.request.logs(4) for a description of the CLF.

EXAMPLES

Example 1

Sample CGI error logs:

{129.146.115.80 [14/Mar/1998:11:03:23 -0800] \\
"GET /cgi-bin/login HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/login} \\
Invalid number of parameters

{129.146.115.80 [14/Mar/1998:12:03:29 -0800] \\
"GET /cgi-bin/sendfile HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/sendfile 1}\\
Unable to open file: /var/http/server/websites/public/profiles/file.1

Output not generated.

{129.146.115.80 [14/Mar/1998:13:03:35 -0800] \\
"GET /cgi-bin/login HTTP/1.0" www.A.com /tmp/tp/root1/cgi-bin/login 2} \\
Authentication failed for user "user1"

Example 2

Sample servlet error logs:

{120.120.120.120 [07/Nov/1998:15:51:52 -0800] \\
"GET /servlet/security HTTP/1.0" www.A.com /servlet/security} 
cannot exec: exec

{120.120.120.120 [07/Nov/1998:15:51:54 -0800] \\
"GET /servlet/network HTTP/1.0" www.A.com /servlet/network}
cannot open url connection: connect

{120.120.120.120 [07/Nov/1998:15:51:56 -0800] \\
"GET /servlet/remote HTTP/1.0" www.A.com /servlet/remote}
 
com.sun.sws.se.ServletSecurityException: file.read
        at com.sun.sws.se.ServletSecurity.checkRead(ServletSecurity.java:473)
        at com.sun.sws.se.ServletSecurity.checkRead(ServletSecurity.java:427)
        at java.io.FileInputStream.(FileInputStream.java)
        at java.io.FileReader.(FileReader.java)
        at RemoteServlet.service(RemoteServlet.java:22)
        at com.sun.sws.se.ServletHandler.servletService(ServletHandler.java:191)
        at com.sun.sws.se.ServletHandler.handle_servlet_service\\
(ServletHandler.java:258)

{- [07/Nov/1998:15:51:57 -0800] "- - -" - -}
SimpleServlet: init

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhtsvl
Interface Stability	Evolving

httpd.site.conf(4)

NAME

httpd.site.conf- Site instance configuration file.

SYNOPSIS

site-path/conf/site_name.site.conf

DESCRIPTION

The site instance configuration file contains directives that define the site's runtime behavior, and defines the identity and server resources used by a web site hosted by the server instance. This file defines properties such as the web site's canonical host name and aliases, the location of the configuration file, and the network connections available to the web site. It also defines the servlet engine settings for the web site. The location of httpd.site.conf is determined by the site_config directive in httpd.conf.

Syntax

The following syntax rules apply to the httpd.site.conf file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored
White space is ignored in directive definitions.
Some directives accept a list of values. Separate multiple values by white space. If more than one line is required to list all values, escape all but the last newline with a backslash (\) at the end of the line.
Any value may optionally be enclosed in double quotes (").
All directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, newlines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks that also use matched curly braces to contain a definition.

The overall format of the file is a list of directives.

See the "Extended Description" for the syntax of all valid directives in each division.

EXTENDED DESCRIPTION

Directives

access_file

Specifies the path in which the server will look for ACLs for each web site hosted by the server instance. Path can be either absolute or relative to site_path. The default is "conf/access.conf".

afp_enable yes | no

Enables Microsoft FrontPage support.

cache_control public | private | no_cache

Sets the caching policy used by intermediate caching proxies. The "public" setting allows the cache to be shared with other proxies. The "private" setting allows the files to be cached, but the cache can not be shared with other proxies. The "no_cache" setting does not allow the cache to be shared with other proxies. The default is "public."

cgi_dns_enable yes | no

cgi_enable yes | no

Enables or disables the authority to execute CGI scripts for the host defined by the url {} block. If enabled, resources in the CGI directory can be accessed through URLs of the form http://hostname/cgi-bin/ and executed as CGI scripts. If enabled and cgi_suffix_enable is also enabled, then any file with a .cgi extension can be executed as a CGI script. Individual sites can override this server setting. The default is "no".

cgi_error_log_cycle_time [[days,]hours:]minutes

Sets the maximum age, in minutes, for CGI error log files for the current host. If a CGI error log is older than the number of cgi_error_log_cycle_time minutes, then a new request log file is started with an incremented sequence number. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. The log cycle time can be specified in days, hours, or minutes. For example, a log cycle time of 24 hours can be 1,0:0 (1 day), 24:0 (24 hours), or 1440 (1440 minutes). Default is 1 day.

cgi_error_log_enable yes | no

Enables or disables CGI script error logging. The default is no.

cgi_error_log_max_files integer

Sets the maximum number of CGI error log files that Sun^TM WebServer^TM will keep for this host. Log files end with a sequence number suffix which is incremented when a new log file is created. If the sequence goes beyond cgi_error_log_max_files, it is reset to 1 and the first CGI error log file is overwritten. This prevents the number of log files from growing without limit. Set cgi_error_log_max_files to "-1" to have no limit on the number of log files. Default is 7 files.

cgi_error_log_max_file_size bytes

cgi_error_log_prefix path/prefix

Sets the directory and log file name prefix for CGI script error logs for a given host. The string can have either an absolute or a relative path followed by the prefix that will be used for this host's log files. Separate virtual hosts must have different prefix names so that there is no conflict in writing to the logs. Each host's log files will have a name in the form:

<pathname>/prefix.<sequence>

For example, <site_path>/logs/error_log.2. Sequence is incremented and a new file created whenever cgi_error_log_cycle_time or cgi_error_log_max_file_size is reached. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. Default is "logs/error_log".

cgi_suffix_enable yes | no

Allows or disallows any file with a .cgi extension to be executed as a CGI script. This can allow users to create CGI without having access to /cgi-bin, and the Sun WebServer administrator has no control over what CGI the server is executing. This is a potential security risk, so consider which .cgi files may be put on your system before enabling this feature. Enabling both user_doc_enable and cgi_suffix_enable is generally risky since it allows any user to execute arbitrary .cgi files through Sun WebServer. Default is "no".

cgi_user username

Sets the user name that will be used to run CGI scripts. By setting the cgi_user, you can control which files and services CGI scripts can affect. The cgi_user must have execute permission for scripts in a host's /cgi-bin directory. Default is "nobody".

content_file path

Specifies the path to the file containing the content for meta data. Path can be either absolute or relative to site_path. Default is "conf/content.conf".

content_digest yes | no

Allows or disallows MD5 checksum to be sent with the response entity. Default is "no".

default_file file [[file]]...

Sets the name of the file Sun WebServer will look for in a directory when a URL request does not name a specific file. For example, if the URL request is for http://hostname/, Sun WebServer will look at the top directory of the host name's doc_root for a file specified as the default_file.

If no file matching the values for default_file is found, the directory contents will be listed, subject to the value of directory_listing.

The built in server-wide default is "index.html". The listings are in order of preference.

directory_listing fancy | simple | off

Specifies how the contents of directories will be listed if no file matching default_file is found in the directory.

fancy: Displays directory contents with each name as a hyperlink to the file, icons matching each file's type, and file size and date information. The icons used and the association of icons to file suffixes is configurable.
simple: Displays only each file name as a hyperlink to the file itself.
off: Disables displaying directory contents; a HTTP "404 Not Found" error is returned to the client instead.

The built-in server-wide default is "fancy".

doc_root relative_path

Sets the top-level directory available to the host for serving web documents. Except for special cases (such as /cgi-bin and users' personal directories), Sun WebServer will only have access to the file system at the doc_root and its subdirectories. This must be set for every host, but it does not have to be unique. You should create a new doc_root for your site.

error_document <http error code< <url>

Allows customized error messages to be returned to the client. Any valid URL, including CGI scripts, may be returned, so you have flexibility in what information you want to give clients when an error occurs. When an HTTP error code is returned, Sun WebServer will return an HTTP "302: Document Moved" header with a Location: header indicating the file to which the error has been remapped. Most clients will automatically fetch the URL named by the Location: header. You can redirect the following HTTP error codes:

400 - Bad Request (Remapped by default host only)
403 - Forbidden
404 - Not Found
412 - Precondition Failed
500 - Server Error
501 - Not Implemented
503 - Service Unavailable

The destination URL can be relative to the current or default host if it begins with a (/). Otherwise, an absolute URL must be specified. The following examples show a relative and absolute URL, respectively:

error_document 503 "/cgi-bin/error.pl?503"
error_document 500 "http://www2.A.com/mirror/"

Note -

The path to which you remap 404 errors must be available in the document root. You can not redirect 404 errors to aliased directories.

icon_add alt_text bitmap_URI file_type[[ file_type]]...

special cases of alt_text = UP | DIR and file_type = ".." or "/"

alt text: Specifies a string that will be used instead of an icon in text-only browsers. For example, "GIF".
URI path to bitmap: Specifies a URI path relative to the default host (in the server {} block) or the host named by the current url {} block. For example, "/icons/binary.xbm".
file suffix(es) | content type(s): Specifies a string of one or more file extensions or content type definitions that will use the icon in "fancy" directory listings.

In addition to file suffixes, you can customize the icon used for "parent directory" (../) and "subdirectory" by specifying "UP" or "DIR" as the alt text.

For example,

icon_add "IMG" "/sws-icons/image.xbm" "gif jpeg xbm"

displays the icon in "/sws-icons/image.xmb" for "gif" "jpeg" and "xbm" files . In text-only browsers, the text "IMG" is displayed.

icon_default bitmap_URI

Sets the icon used for files with extensions that do not have a defined icon type. The path to the bit map file must begin with a (/), and it is relative to the default host or the host defined by the current url {} block.

log_cycle_time [[days,]hours:]minutes

Sets the maximum age for request log files for the current host. If a request log is older than the number of log_cycle_time minutes, then a new request log file is started with an incremented sequence number. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. The log cycle time can be specified in days, hours, or minutes. For example, a log cycle time of 24 hours can be 1,0:0 (1 day), 24:0 (24 hours), or 1440 (1440 minutes). Default is 1 day.

log_max_files integer

Sets the maximum number of request log files that Sun WebServer will keep for this host. Log files end with a sequence number suffix which is incremented when a new log file is created. If the sequence goes beyond log_max_files, it is reset to 1 and the first request log file is overwritten. This prevents the number of log files from growing without limit. Set log_max_files to "-1" to have no limit on the number of log files. Default is 7 files.

log_max_size bytes

Sets the maximum file size, in bytes, for request log files for the current host. If a request log exceeds log_max_size, a new log file is started with an incremented sequence number. Default is 1048576 bytes (1 MB).

log_prefix path/prefix

Sets the directory and log file name prefix for request logs for a given host. The string can have either an absolute or a relative path followed by the prefix that will be used for this host's log files. Separate virtual hosts must have different prefix names so that there is no conflict in writing to the logs. Each host's log files will have a name in the form:

<pathname>/prefix.<log_type>.<sequence>

For example, <site_path>/logs/http_log.elf.2. Sequence is incremented and a new file created whenever log_cycle_time or log_max_size is reached. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. Default is "logs/http_log".

log_translate_ip_address yes | no

Determines whether a given virtual host logs its IP address or DNS name into its log files. Default is "no" and the IP address is logged.

log_type none | clf | elf | eclf

Sets the format for a host's request logs. Valid parameters are:

none: Disallows logging performed for this host.
clf: Logs in common log file format, a format widely used by servers and analysis tools.
elf: Logs in extended log file format.
eclf: Logs in extended common log file format; provides more fields than common log format.

If log_type is not "none", then log_prefix must be set. Default is "elf".

map_file filename

Specifies the location of the web site's map file. Path can be either absolute or relative to site_path. For information on maps, see the man page for map.conf(4)Default is "conf/map.conf".

mime_default_type type/subtype

Sets the MIME type that will be used for files whose extension do not match any other MIME type. The default is "text/html".

mime_file relative_path

Contains the default MIME types definitions used for the server host. Path is relative to site_path. Default is "mime.types".

If no MIME type for the file can be found, the mime_default_type is used. Entries in the mime_file have the form:

<media type>/<media subtype><file suffix(es)>

For example: text/html html htm The default server-wide mime_file is /etc/http/mime.types.

publish_enable yes | no

Allows or disallows HTTP methods PUT and DELETE. The default is "no".

If publish_enable is set to "yes," Sun WebServer implements HTTP PUT and DELETE requests by redirecting the requests to the executable script located in server_root/cgi-bin/publish_script. This CGI script provides the publishing support for the server. If you create your own publish_script, install it in this directory to replace the implementation provided. The original C source code is provided in /usr/http/src/put/putscript.c so that you can modify the code to suit your individual needs. In the sample server instance sws_server, the server root is /var/http/sws_server/, so the script is located in /var/http/sws_server/cgi-bin/publish_script.

Note -

If you enable publishing, you may want to use access control to restrict the users who can use PUT and DELETE methods. Otherwise, any user with access to the web site can modify it using PUT and DELETE. Because Sun WebServer handles many requests simultaneously, it is possible that a PUT or DELETE request is processed in a time interval that overlaps with a GET request for the same file. In some cases, the results of such a GET request may be truncated or contain no data. Subsequent requests (after the PUT and DELETE request has completed) will behave as expected.

realm_file path

Specifies path to the file containing realm information. Path can be either absolute or relative to site_path. Default is "conf/realms.conf".

se_enable yes | no

Enables or disables the servlet engine. The default is "no".

servlet_token URI path

Specifies the token which characterizes the request as a servlet request. Default is "/servlet".

ssi_enable yes | no

Enables or disables the ability to use server-side include statements in .shtml files. May be set differently for each virtual host on the server. Default is "no".

ssi_exec yes | no

Enables or disables the ability to use #exec server-side include directive. #exec will execute shell commands or CGI scripts, which may pose security risks and/or slow performance. Default is "no".

ssi_suffix string

Specifies SSI file suffix. Default is ".shtml".

ssi_xbithack full | on | off

Allows any file in the document root with its executable bit set to be treated as a server-parsed HTML file. ssi_suffix can be "full" or "on" only if ssi_enable is "yes". If "full", Sun WebServer treats any file with the user or group executable bit set as server-parsed HTML, and it sends the file's Last-Modified time in the HTTP header if the user executable bit is set. If "on", Sun WebServer only treats files with the user's executable bit set as server-parsed HTML. Default is "off".

Note -

If cgi_suffix_enable is also enabled, Sun WebServer will check to see if an executable file is a CGI script before parsing it for server-side includes.

symlink_follow yes | no

user_doc_enable yes | no

Allows or disallows UNIX users to create personal HTML directories in their home directories. Default is "no".

See the "NOTESNOTES" section for information on user directories in a Solaris ISP Server environment.

user_doc_root relative_path

Sets the directory name that users can create in their home directories for personal HTML files. When a request comes in for //server/~username/, Sun WebServer will look for files in ~username/<user_doc_root>/. Enables access. Default is "public_html".

See the "NOTESNOTES" section for information on user directories in a Solaris ISP Server environment.

user_doc_source source

In Solaris ISP Server, if virtual FTP servers have been defined in Sun Directory Services, you may set this to ISP. User information will be taken from the directory server, and the value of a user's ispContentDirectory will be used.

See the NOTESNOTES section for information on user directories in a Solaris ISP Server environment.

servlet_engine{} Directives

Specifies parameters of the servlet engine

chaining_enable yes | no

Enables or disables servlet chaining. This enables the servlet engine to run a sequence of servlets in a specified order to fulfil one single servlet request. Host administrators can specify a chain of servlets to be executed sequentially. Default is "yes".

cookie_comment comment

Specifies the value of the comment field in cookies with session IDs. Default is "Sun Web Server Session Tracking Cookie".

cookie_domain domain

cookie_max_age seconds

Specifies the value of the max-age field sent for cookies with session IDs. A cookie with cookie_max_age 0 expires immediately.

cookie_name name

Specifies the name of a cookie used to carry the session ID when cookies are enabled. Default is "swssessionid".

cookie_path path

Specifies the value of the path field sent for cookies with session IDs. This allows you to set the URL path within which the cookie is valid. Pages outside of this path cannot read the cookie. This path is relative to site_path. Default is "/".

cookie_secure yes | no

dynamic_linking_enable all | local | remote | none

Allows the specified servlets access to dynamic libraries. Default is "local".

file_access_enable all | local | remote | none relative_path

Allows specified servlets to have access to file resources, for example, read/write a file on local disk. Default is "local".

network_access_enable all | local | remote | none

Allows specified servlets to have access to network resources e.g. open a socket. Default is "local".

reload_enable yes | no

remote_enable yes | no

Enables or disables remote servlets. Enabling remote servlets allows the servlets from remote sites to be loaded by the server. The default is "yes".

properties_file path

Path to the "servlets.properties" file. Each servlet engine instance can have a list of preloaded servlets that it wishes to load and initialize as soon as the server starts. This list is specified in a servlet properties file. Path can be either absolute or relative to site_path. Default is "conf/servlets.properties".

servlets_path absolute_path

Specifies the path to all loadable local servlets. This is a colon separated list of directories and jar files where the servlet engine will look for servlets (for example, /directory/directory:/directory/directory). Default is "site_path/servlets".

se_log_enable yes | no

Enables or disables the servlet error logging. The default is "no".

se_log_cycle_time [[days,]hours:]minutes

Sets the maximum age for servlet error log files for the current host. If a servlet error log is older than the number of se_log_cycle_time minutes, then a new servlet error log file is started with an incremented sequence number. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. The log cycle time can be specified in days, hours, or minutes. For example, a log cycle time of 24 hours can be 1,0:0 (1 day), 24:0 (24 hours), or 1440 (1440 minutes). Default is 1 day.

se_log_max_files integer

se_log_max_file_size bytes

Sets the maximum file size, in bytes, for servlet error log files for the current host. If a servlet error log exceeds se_log_max_file_size, a new log file is started with an incremented sequence number. Default is 1048576 bytes (1 MB).

se_log_prefix path/prefix

Sets the directory and log file name prefix for servlet error logs for a given host. The string must have either an absolute or relative path name followed by the prefix that will be used for this servlet engine's log files. Separate servlet engines must have different prefix names so that there is no conflict in writing to the logs. Each servlet engines' log files will have a name in the form:

<pathname>/prefix.<sequence>

For example, <site_path>/logs/se_log.2. Sequence is incremented and a new file created whenever se_log_cycle_time or se_log_max_file_size is reached. If a log file contains no entries, then no new log file will be generated regardless of how much time has passed. Default is "logs/se_log".

security_access_enable all | local | remote | none path/prefix

Allows the specified servlets to have access to security resources, for example, classLoaders. The path must be an absolute path. Default is "none".

send_auth_hdrs yes | no

Specifies whether to send authorization headers to servlets. Authorization headers hold information about client authentication such as encoded user name and password. Default is "no".

session_invalidation_time [[days,]hours:]minutes

Specifies the length of time that a sesssion is allowed to remain unused before it is invalidated. Default is 30 minutes.

session_max_residents integer

session_protocol_switch_rewriting yes | no

Specifies whether session ID is added to URLs when URL dictates a switch from "http" to "https" or vice-versa. Used only in servlet URL rewriting. Default is "no".

session_swap_directory path

Specifies the directory path where the swapped sessions reside. The path can be either absolute or relative to site_path.

singlethreadmodel_init_pool_size integer

Specifies the initial number of instances of a single servlet to be spawned in the case of SingleThreadModel servlets. Default is 5.

singlethreadmodel_max_pool_size integer

Specifies the maximum number of instances of a single servlet to be spawned in the case of SingleThreadModel servlets. Default is 20.

system_access_enable all | local | remote | none

Allows or disallows the specified servlets to have access to system resources, for example, call System.Exec(). Default is "local".

EXAMPLES

Example 1

A sample web site configuration file with an enabled servlet engine:

#
# Copyright (c) 1998, by Sun Microsystems, Inc.
# All rights reserved.
#
# Sun WebServer Site Configuration 

url  {
    doc_root    /var/http/sws_server/websites/www.A.com/public
    log_type    eclf
    user_doc_enable     yes

    map_file            conf/map.conf
    realm_file          conf/realms.conf
    access_file         conf/access.conf
    content_file        conf/content.conf

    # If you need more than the global mime types in 
    # /etc/http/mime.types, create this file:
    #
    # mime_file         conf/mime.types

    se_enable                     yes 
    servlet_token                 "/servlet/"
    servlet_engine {
        properties_file        /var/http/sws_server/websites/\\
				www.A.com/conf/servlets.properties
        servlets_path          //var/http/sws_server/websites/\\
				www.A.com/servlets/
        se_log_prefix          "/var/http/logs/A.com_se_log"
        se_log_enable          yes
        se_log_max_files       7
        se_log_max_file_size   1048576
        se_log_cycle_time      1,0:0 

        reload_enable          yes
        remote_enable          yes
        chaining_enable        yes
        network_access_enable         local
        file_access_enable            local
        dynamic_linking_enable        local
        system_access_enable          local 
        security_access_enable        local

        session_swap_directory        "/tmp/sessionSwap"
        session_max_residents         500
        cookie_name                   "specialSessionId"
        cookie_comment                "Session Tracking Cookie"
    }
}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

If you are running on the Solaris^TM ISP Server^TM software, user information (including user content directories) can be accessed through LDAP and Sun Directory Services.

To use LDAP for user content directories, a virtual FTP site matching the Sun WebServer web site (virtual host) must exist in the Directory Services. Refer to the Sun^TM Internet FTP Server 1.1 online help for information on creating virtual FTP sites.

If user_doc_source is set to "ISP," Sun WebServer will attempt to map ~user URLs to the value of ispContentDirectory in Sun Directory Services.

The ispContentDirectory is relative to the ispRootDirectory defined in the ispService entry for a virtual FTP site. The file system directory must be readable and writable by either the uidNumber or gidNumber defined in a subscriber's entry in the directory service.

When the CGI and servlet logs are enabled, they capture output from the standard error streams of CGI scripts and servlets in cycled log file sets that Sun WebServer manages. Enabling these logs can impair Sun WebServer's throughput because scripts and servlets often use the log files for debugging messages which can flood the log files; this file system traffic can degrade performance on a heavily loaded web site. However, to debug CGI scripts and servlets, or to record all the CGI and servlet output, you must enable the error log. You can minimize the disk space requirements by carefully choosing the cycling parameters from the web site management screens in the Sun WebServer GUI.

All non-servlet related directives (other than servlet_token) are not explicitly supported in the command-line utilities. If they are modified through an editor, then the synchronization of file writes are handled through UNIX (outside of the file locking mechanism used by both the administration and the command-line utilities). This could lead to file inconsistencies not encountered if one performed management exclusively through the Sun WebServer GUI.

Sun WebServer 2.1 Last Revised 22 February 1999

map.conf(4)

NAME

map.conf- Creates an alias to a path on the file system or a redirection to a remote URL from a URI on the host.

SYNOPSIS

site_path/conf/map.conf

DESCRIPTION

A map directive allows you to redirect requests for a URL on a host to any other URL or to a different directory. htmap administers maps to establish an alias to another resource, make a resource outside of the doc_root accessible to a client, or partition the name space into various classes of resources such as CGI, imagemap, or servlet. The URL token that is redirected does not have to correspond to any actual resource.

Servlets use maps for creating servlet chains or file aliases.

A map definition consists of the following:

URI token
Resource target
Class type (optional)

Syntax

Each line in the map.conf file has the following format:

uri_token			resource_target			class_type

URI_token

Specifies a URI path on the given host beginning with a slash (/).

resource_target

Specifies a URI path on the given host if it begins with a slash (/), or an absolute URL to any network location if it does not begin with a (/). For either local or remote redirects, class_type must be REMOTE. It can also be an absolute path on the file system if it begins with a (/) and the class_type is ADMIN, CGI, IMAP, NULL, SERVLET, or STATS.

class_type

Specifies the class type. Valid entries are as follows:

Note -

class_type is not case sensitive.

ADMIN: Treats the resource target as the Sun WebServer administration directory.
CGI: Treats the resource target as a CGI directory. All files located here will be treated as executable scripts.
DOOR: Treats the aliased file or directory as a resource door. Resource doors are multithreaded server daemons which run independently of the web server. With resource doors, Sun WebServer is able to pass incoming requests on to user-developed programs through the Solaris ^TMdoors mechanism. For more information on Sun WebServer resource doors, refer to the "Site URL Aliases Screen" section in the online help.
IMAP: Treats the resource target as an imagemap alias.
NULL: Treats the resource target as a regular file alias.
REMOTE: Treats the resource target as a remote alias.
STATS: Treats the resource target as an interface to server statistics.
SERVLET: Treats the resource target as a servlet or a chain of servlets. URLs which begin with the aliased token are treated as requests for servlets.

EXAMPLES

Example 1

A directory alias can specify "CGI" as a class token, and all files in the directory and its subdirectories will be treated as CGI scripts. Typically, each host has a map directive to define the location of /cgi-bin. An example of creating an alias for the /cgi-bin is

map "/cgi-bin" "/var/http/www/cgi/" CGI

Example 2

A directory alias can also specify "SERVLET" as a class token, and the aliased resource_target is treated as a servlet or a chain of servlets. An example of creating an alias for the resource_target is

map "/servlets" "servlet1" SERVLET

where "servlet1" is a servlet defined in servlet.properties.

Another example of creating an alias for the resource_target is

map "/combo" "S1,S2" SERVLET

where "/combo" defines a chain of servlets and "S1" and "S2" are servlets defined in servlet.properties.

Example 3

If map has only one parameter, it disables any redirects or aliases for that token.

map		/cgi-bin			/var/http/public/x/y			CGI
map		/search			/searchServlet			SERVLET
map		/home.html		/var/http/docs/index.html		NULL

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

realms.conf(4)

NAME

^TM

SYNOPSIS

site_path/conf/realms.conf - Web site realms

/etc/http/realms.conf - Server realms for server administration

DESCRIPTION

Realms in Sun^TM WebServer^TM define sets of protection spaces or authentication domains consisting of user names, groups, and passwords. Sun WebServer uses realm information to determine how a user is authenticated. For example, a UNIX-based realm stores user and password information as well as group information in appropriate files or tables if distributed NIS/NIS+ is used. For HTPASSWD relams, you can define your own set of users and groups in a realm. Regardless of how the realm information is stored and accessed, the access control settings require realms to protect resources.

Realms are also differentiated based on how they are used. Two different realms can have different names with the same underlying users and groups database. This gives additional flexibility in naming the authentication domains displayed in the browser.

Most browsers display the realm name in the prompt when a user name and password are required, so the realm name should indicate to users the purpose for password protection and which user name and password to use.

Realm files may be created by htrealm(1m) or by the Sun WebServer GUI.

A realm definition consists of the following:

Realm identifier
Source of user information: HTPASSWD, ISP, ISPADMIN, or UNIXSYS

Note -
ISP or ISPADMIN realms are only valid if you are running Sun WebServer in an environment where Sun Directory Service for the Solaris ISP Server^TM software has been installed.
List of realm members with permission to modify the realm itself
Directory location of user information for HTPASSWD realms

Syntax

The following syntax rules apply to the realms.conf file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored
White space is ignored in directive definitions.
Some directives accept a list of values. Separate multiple values by white space. If more than one line is required to list all values, escape all but the last newline with a backslash (\) at the end of the line.
All directives are grouped in blocks surrounded by curly braces ({ and }). Any amount of white space, newlines, or directive definitions may appear between an opening curly brace and its matching close, including directive blocks that also use matched curly braces to contain a definition.

Each realm definition is in the following form:

realm <identifier> {
   realm_source UNIXSYS | ISP | ISPADMIN | HTPASSWD
   [ realm_dir <data_directory> ]
   administrator {
      [user <realm_user_name>[ <realm_user_name>...]]
      [ group <realm_group_name>[ <realm_group_name>...] ]
   }
}

The syntax and definition of each directive are explained in the following Directives section.

Directives

The following keyword directives are valid in the realms.conf file:

administrator { admins }

Defines the realm users and groups that have permission to modify realm data. The admins directive may have a user directive or have a group directive. If neither user nor group is specified, then the site administrator becomes the default administrator.

group group_name[[ group_name...]]

Names groups of users that have permission to modify realm data. The group_name directive is an optional directive valid in the administrator block. Separate multiple group names with white space.

isp_component component_id_version

Defines the component identification, the version of Solaris ISP Server, and the Administrator realm (ISPADMIN). The default value is "SUNWhttp-2.1".

realm identifier { definition }

Defines a realm. There may be multiple realm definitions in the realms.conf file, as long as each has a unique identifier. The identifier directive can be any arbitrary string of alphanumeric data (no special characters). White space is allowed when enclosed in double quotes.

The definition consists of realm directives, and must include at least a realm_source.

[[realm_dir data_path]]

Defines a directory relative to the site path where the users and groups files for an HTPASSWD realm are stored. realm_dir is required and valid only if realm_source is HTPASSWD. It can be either an absolute path or a path relative to realms.conf, or it can be left unspecified. The default value is realms/realmname/.

realm_source source

Defines the source of user and group information for the realm. This directive is required in every realm definition. realm_source may be one of the following:

HTPASSWD: Indicates that the user or group information is retrieved using the Sun WebServer users/group file format, and that user and group information will be maintained in the data directory named by realm_dir. The htrealm(1m) utility is used to create users and modify passwords.
ISP: Indicates that the user or group is stored in the Solaris ISP Server shared directory service. Changes to user and group information cannot be made through Sun WebServer.
ISPADMIN: Indicates that the principals are administrators in the Solaris ISP Server Sun^TM Internet Administrator^TM. The -d flag takes the ISP-component ID and version (for example, "SUNWftp-2.0").
UNIXSYS: Indicates that the operating system user and group definitions will be used to authenticate users in the realm. Sun WebServer employs a standard Pluggable Authentication Module (PAM) for authentication. Changes to user and group information cannot be made through Sun WebServer.

user user_name[[ user_name...]]

Names realm users that have permission to modify realm data. The user_name can be specified in the administrator block. Separate multiple user names with white space.

EXAMPLES

Example 1

/etc/pam.conf

httpd auth sufficient /usr/lib/security/pam_unix.so.1
httpd-isp auth sufficient /usr/lib/security/pam_ldap.so.1 autohost

This configures Sun WebServer httpd to use the UNIX PAM library for authenticating for Solaris ISP Serversubscribers stored in the LDAP-based directory. This does not use stacking, but uses different service names (httpd, httpd-isp).

Example 2

Sample realms.conf file:

realm siteAdmin { 
        realm_source HTPASSWD
        administrator { 
                user user1
         }

}

realm SystemUsers { 
        realm_source UNIXSYS

}

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

Sun WebServer on Solaris 2.6 and greater uses a Pluggable Authentication Module (PAM) for authenticating principals in UNIXSYS and ISP realms using /usr/lib/security/pam_unix.so, and /usr/lib/security/pam_ldap.so, respectively. Refer to pam.conf(4) for details on how to set up PAM.

Sun WebServer 2.1 Last Revised 22 February 1999

servlets.properties(4)

NAME

^TM

SYNOPSIS

site_path/conf/servlets.properties

DESCRIPTION

This file contains the name of each servlet and the initialization parameters of the servlet. You can either place the properties file in the default location, or specify the name of the servlets.properties file on start-up using the command htservlet and specifying -i hostname for the host name and -p properties_file for the name of the properties file.

The servlet.properties file may be updated using the Sun^TM WebServer^TM GUI or the htservlet(1m) utility.

You can specify the following servlet properties definitions:

Code
Code base
Initial arguments

Syntax

The definitions in the servlets.properties file have the following format:

servlet.<servlet_name>.code=<servletclass>
servlet.<servlet_name>.codebase=<URL>
servlet.<servlet_name>.initArgs=<name>=<value>[,<name>=value...]

The following keyword directives are valid in the servlet.properties file:

servlet.<servlet_name>.code=<servletclass>: Names the name of the servlet main class file.
servlet.<servlet_name>.codebase=<URL>: Names the jar file or the URL of the servlet's codebase. Used only for remote servlets.
servlet.<servlet_name>.initArgs=<name>=<value>[,<name>=value...]: Defines the optional initial arguments passed to the servlet. Used in the format name=value [[, name=value...]]

EXAMPLES

Example 1

A sample servlets.properties based on the default file:

#
# Copyright (c) 1998, by Sun Microsystems, Inc.
# All rights reserved.
#
# servlets.properties
#
#       Sample SWS Servlets Properties File
#
##############################################################################


# the list of servlets to be loaded at startup time
servlets.startup=simple hello


# Date Servlet -- JSDK Sample Servlet 
servlet.date.code=DateServlet

# Finger Servlet -- JSDK Sample Servlet
servlet.finger.code=FingerServlet

# Hello World  Servlet -- JSDK Sample Servlet
servlet.hello.code=HelloWorldServlet

# Snoop Servlet -- JSDK Sample Servlet
servlet.snoop.code=SnoopServlet
servlet.snoop.initArgs= port=23, host=localhost

# Simple Servlet -- JSDK Sample Servlet
servlet.simple.code=SimpleServlet

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

users(4)

NAME

HTPASSWD

SYNOPSIS

site_path/conf/realms/HTPASSWD_realm/users

DESCRIPTION

The users file lists the users in an HTPASSWD realm.

A user definition consists of a user name and password. You may add new users to the users file by htrealm(1m)or by the Sun WebServer GUI. To change a user's password, use htpasswd(1m) or the Sun WebServer GUI.

The password is displayed with BASE64 encoding. If you have installed FrontPage Apache Emulator, this field may be in UNIX encrypted format.

Syntax

The following syntax rules apply to the users file:

The pound sign (#) is a comment character. All characters from a # to the end of a line are ignored
White space is ignored in user definitions.

Each user definition is in the following form:

username:encoded_password

EXAMPLES

Example 1

Sample users file:

# the user name and password database
	user1:YmFycnk=
	user2:YWRtaW4=
	user3:YHUvwaAx=
	user4:YTkoiWAt=

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWhttpc
Interface Stability	Evolving

NOTES

Do not edit users manually. Use htrealm(1m) to add or delete users, and htpasswd(1m) to set or edit passwords.

Sun WebServer 2.1 Last Revised 22 February 1999

Previous: man Pages(1m): Maintenance Commands

man Pages(4): File Formats

htIntro(4)

NAME

DESCRIPTION

ATTRIBUTES

FILES

SEE ALSO

NOTES

access.conf(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

Directives

EXAMPLES

Example 1

Example 2

ATTRIBUTES

SEE ALSO

NOTES

content.conf(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

Directives

EXAMPLES

Example 1

Example 2

ATTRIBUTES

SEE ALSO

groups(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

EXTENDED DESCRIPTION

EXAMPLES

Example 1

ATTRIBUTES

SEE ALSO

NOTES

httpd-instances.conf(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

Directives

EXAMPLES

Example 1

ATTRIBUTES

SEE ALSO

NOTES

httpd.conf(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

EXTENDED DESCRIPTION

server {} Block Directives

url {} Block Directives

port {} Block Directives

EXAMPLES

Example 1

ATTRIBUTES

SEE ALSO

NOTES

httpd.event.logs(4)

NAME

SYNOPSIS

DESCRIPTION

Syntax

EXAMPLES

Example 1

ATTRIBUTES

SEE ALSO

NOTES

httpd.request.logs(4)

NAME

SYNOPSIS

`server {}` Block Directives

`url {}` Block Directives

`port {}` Block Directives