Satisfy directive
Syntax: Satisfy 'any' or 'all'
Default: Satisfy all
Context: directory, .htaccess
Status: core
Compatibility: Satisfy is only available in Apache 1.2 and later
Access policy if both allow and require used. The parameter can be either 'all' or 'any'. This directive is only useful if access to a particular area is being restricted by both username/password and client host address. In this case the default behavior ("all") is to require that the client passes the address access restriction and enters a valid username and password. With the "any" option the client will be granted access if they either pass the host restriction or enter a valid username and password. This can be used to password restrict an area, but to let clients from particular addresses in without prompting for a password.
See also require and mod_access.
--------------------------------------------------------------------------------
ScoreBoardFile directive
Syntax: ScoreBoardFile filename
Default: ScoreBoardFile logs/apache_status
Context: server config
Status: core
The ScoreBoardFile directive is required on some architectures to place a file that the server will use to communicate between its children and the parent. The easiest way to find out if your architecture requires a scoreboard file is to run Apache and see if it creates the file named by the directive. If your architecture requires it then you must ensure that this file is not used at the same time by more than one invocation of Apache.
If you have to use a ScoreBoardFile then you may see improved speed by placing it on a RAM disk. But be careful that you heed the same warnings about log file placement and security.
Apache 1.2 and above:
Linux 1.x users might be able to add -DHAVE_SHMGET -DUSE_SHMGET_SCOREBOARD to the EXTRA_CFLAGS in your Configuration. This might work with some 1.x installations, but won't work with all of them. (Prior to 1.3b4, HAVE_SHMGET would have sufficed.)
SVR4 users should consider adding -DHAVE_SHMGET -DUSE_SHMGET_SCOREBOARD to the EXTRA_CFLAGS in your Configuration. This is believed to work, but we were unable to test it in time for 1.2 release. (Prior to 1.3b4, HAVE_SHMGET would have sufficed.)
See Also: Stopping and Restarting Apache
--------------------------------------------------------------------------------
ScriptInterpreterSource directive
Syntax: ScriptInterpreterSource 'registry' or 'script'
Default: ScriptInterpreterSource script
Context: directory, .htaccess
Status: core (Windows only)
This directive is used to control how Apache 1.3.5 and later finds the interpreter used to run CGI scripts. The default technique is to use the interpreter pointed to by the #! line in the script. Setting ScriptInterpreterSource registry will cause the Windows Registry to be searched using the script file extension (e.g., .pl) as a search key.
--------------------------------------------------------------------------------
SendBufferSize directive
Syntax: SendBufferSize bytes
Context: server config
Status: core
The server will set the TCP buffer size to the number of bytes specified. Very useful to increase past standard OS defaults on high speed high latency (i.e., 100ms or so, such as transcontinental fast pipes)
--------------------------------------------------------------------------------
ServerAdmin directive
Syntax: ServerAdmin email-address
Context: server config, virtual host
Status: core
The ServerAdmin sets the e-mail address that the server includes in any error messages it returns to the client.
It may be worth setting up a dedicated address for this, e.g.
ServerAdmin www-admin@foo.bar.com
as users do not always mention that they are talking about the server!
--------------------------------------------------------------------------------
ServerAlias directive
Syntax: ServerAlias host1 host2 ...
Context: virtual host
Status: core
Compatibility: ServerAlias is only available in Apache 1.1 and later.
The ServerAlias directive sets the alternate names for a host, for use with name-based virtual hosts.
See also: Apache Virtual Host documentation
--------------------------------------------------------------------------------
ServerName directive
Syntax: ServerName fully-qualified domain name
Context: server config, virtual host
Status: core
The ServerName directive sets the hostname of the server; this is used when creating redirection URLs. If it is not specified, then the server attempts to deduce it from its own IP address; however this may not work reliably, or may not return the preferred hostname. For example:
ServerName www.example.com
would be used if the canonical (main) name of the actual machine were simple.example.com.
If you are using name-based virtual hosts, the ServerName inside a <VirtualHost> section specifies what hostname must appear in the request's Host: header to match this virtual host.
See Also:
DNS Issues
Apache virtual host documentation
UseCanonicalName
NameVirtualHost
ServerAlias
--------------------------------------------------------------------------------
ServerPath directive
Syntax: ServerPath pathname
Context: virtual host
Status: core
Compatibility: ServerPath is only available in Apache 1.1 and later.
The ServerPath directive sets the legacy URL pathname for a host, for use with name-based virtual hosts.
See also: Apache Virtual Host documentation
---------------------------------------------------
