Spade
Mini Shell
<!DOCTYPE html>
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible"
content="IE=edge,chrome=1" />
<title>LiteSpeed Web Server Users' Manual - Server
General</title>
<meta name="description" content="LiteSpeed Web Server
Users' Manual - Server General." />
<meta name="viewport" content="width=device-width,
initial-scale=1.0" />
<meta name="robots" content="noindex">
<link rel="shortcut icon" href="img/favicon.ico"
/>
<link rel="stylesheet" type="text/css"
href="css/hdoc.css">
</head>
<body>
<div class="pagewrapper clearfix"><aside
class="sidetree ls-col-1-5">
<figure>
<img src="img/lsws_logo.svg" alt="lightspeed web
server logo"
width="100px"/>
</figure>
<h2 class="ls-text-thin">
LiteSpeed Web Server
<br />
<span class="current"><a
href="index.html">Users' Manual</a></span>
</h2>
<h3 class="ls-text-muted">Version 6.3
— Rev. 0</h3>
<hr/>
<div>
<ul>
<li><a href="license.html">License
Enterprise</a></li>
<li><a
href="intro.html">Introduction</a></li>
<li><a
href="install.html">Installation</a></li>
<li>
<a href="admin.html">Administration</a>
<ul class="menu level2">
<li><a href="ServerStat_Help.html">Service
Manager</a></li>
<li><a
href="Real_Time_Stats_Help.html">Real-Time
Stats</a></li>
</ul>
</li>
<li><a
href="security.html">Security</a></li>
<li>
<a href="config.html">Configuration</a>
<ul class="level2">
<li><span class="current"><a
href="ServGeneral_Help.html">Server
General</a></span></li>
<li><a href="ServLog_Help.html">Server
Log</a></li>
<li><a href="ServTuning_Help.html">Server
Tuning</a></li>
<li><a href="ServSecurity_Help.html">Server
Security</a></li>
<li><a href="Cache_Help.html">Page
Cache</a></li>
<li><a
href="PageSpeed_Config.html">PageSpeed
Config</a></li>
<li><a href="ExtApp_Help.html">External
Apps</a></li>
<ul class="level3">
<li><a href="External_FCGI.html">Fast CGI
App</a></li>
<li><a
href="External_FCGI_Auth.html">Fast CGI
Authorizer</a></li>
<li><a href="External_LSAPI.html">LSAPI
App</a></li>
<li><a
href="External_Servlet.html">Servlet
Engine</a></li>
<li><a href="External_WS.html">Web
Server</a></li>
<li><a href="External_PL.html">Piped
logger</a></li>
<li><a href="External_LB.html">Load
Balancer</a></li>
</ul>
<li><a
href="ScriptHandler_Help.html">Script
Handler</a></li>
<li><a
href="PHP_Help.html">PHP</a></li>
<li><a href="App_Server_Help.html">App
Server Settings</a></li>
<li><a
href="Listeners_General_Help.html">Listener
General</a></li>
<li><a
href="Listeners_SSL_Help.html">Listener
SSL</a></li>
<li><a href="Templates_Help.html">Virtual
Host Templates</a></li>
<li><a
href="VirtualHosts_Help.html">Virtual Host
Basic</a></li>
<li><a href="VHGeneral_Help.html">Virtual
Host General</a></li>
<li><a href="VHSecurity_Help.html">Virtual
Host Security</a></li>
<li><a href="VHSSL_Help.html">Virtual Host
SSL</a></li>
<li>
<a href="VHPageSpeed_Config.html">Virtual Host
PageSpeed Config</a>
</li>
<li><a
href="Rewrite_Help.html">Rewrite</a></li>
<li><a
href="Context_Help.html">Context</a></li>
<ul class="level3">
<li><a href="Static_Context.html">Static
Context</a></li>
<li>
<a href="Java_Web_App_Context.html">Java Web
App Context</a>
</li>
<li><a
href="Servlet_Context.html">Servlet
Context</a></li>
<li><a href="FCGI_Context.html">Fast CGI
Context</a></li>
<li><a href="LSAPI_Context.html">LSAPI
Context</a></li>
<li><a href="Proxy_Context.html">Proxy
Context</a></li>
<li><a href="CGI_Context.html">CGI
Context</a></li>
<li><a href="LB_Context.html">Load
Balancer Context</a></li>
<li><a
href="Redirect_Context.html">Redirect
Context</a></li>
<li><a href="App_Server_Context.html">App
Server Context</a></li>
<li><a
href="Rails_Context.html">Rack/Rails
Context</a></li>
</ul>
<li><a
href="VHAddOns_Help.html">Add-ons</a></li>
</ul>
</li>
<li>
<a href="webconsole.html">Web Console</a>
<ul class="level2">
<li><a href="AdminGeneral_Help.html">Admin
Console General</a></li>
<li><a href="AdminSecurity_Help.html">Admin
Console Security</a></li>
<li>
<a href="AdminListeners_General_Help.html">
Admin Listener General
</a>
</li>
<li>
<a href="AdminListeners_SSL_Help.html">Admin
Listener SSL</a>
</li>
</ul>
</li>
</ul>
</div>
</aside>
<article class="contentwrapper ls-col-3-5 clearfix"><div
class="nav-bar ls-spacer-micro-top"><div
class="prev"> </div><div
class="center"><a
href="config.html">Configuration</a></div><div
class="next"><a
href="ServLog_Help.html">Server Log</a>
»</div></div>
<h1>Server General</h1><section
class="ls-spacer-small-bottom">General settings for the whole
server. When path information is required in a setting,
it can be either absolute or relative to $SERVER_ROOT. $SERVER_ROOT is the
location where LiteSpeed web server has been installed (your_home_dir/lsws
or
/opt/lsws, for example). The server executable is under
$SERVER_ROOT/bin.</section>
<h2 id="top">Table of Contents</h2><section
class="toc"><section
class="toc-row"><header>Server
Process</header><p>
<a href="#serverName">Server Name</a> | <a
href="#lswsProcesses">Number of Processes</a> | <a
href="#runningAs">Running As</a> | <a
href="#serverPriority">Priority</a> | <a
href="#cpuAffinity">CPU Affinity</a> | <a
href="#servChrootPath">Chroot Path</a> | <a
href="#enableChroot">Enable chroot</a> | <a
href="#enableLVE">Cloud-Linux</a> | <a
href="#inMemBufSize">Max I/O Buffer Size</a> | <a
href="#swappingDir">Swapping Directory</a> | <a
href="#autoFix503">Auto Fix 503 Error</a> | <a
href="#enableh2c">Enable HTTP/2 Over Cleartext TCP</a> |
<a href="#gracefulRestartTimeout">Graceful Restart Timeout
(secs)</a></p></section>
<section class="toc-row"><header>General
Settings</header><p>
<a href="#mime">MIME Settings</a> | <a
href="#mimesuffix">Suffixes</a> | <a
href="#mimetype">MIME Type</a> | <a
href="#disableInitLogRotation">Disable Initial Log
Rotation</a> | <a href="#showVersionNumber">Server
Signature</a> | <a href="#hideSigInErrorPage">Hide
Error Page Signature</a> | <a
href="#enableIpGeo">Enable GeoLocation Lookup</a> |
<a href="#useIpInProxyHeader">Use Client IP in
Header</a> | <a href="#extAppAbort">External
Application Abort</a> | <a
href="#autoUpdateInterval">Check For Update</a> | <a
href="#autoUpdateDownloadPkg">Download Updates</a> |
<a href="#adminEmails">Administrator
Email</a></p></section>
<section class="toc-row"><header>Index
Files</header><p>
<a href="#indexFiles">Index Files</a> | <a
href="#autoIndex">Auto Index</a> | <a
href="#autoIndexURI">Auto Index
URI</a></p></section>
<section class="toc-row"><header><a
href="#htaccess">HT Access</a></header><p>
<a href="#allowOverride">Allow Override</a> | <a
href="#accessFileName">Access File
Name</a></p></section>
<section class="toc-row"><header>Expires
Settings</header><p>
<a href="#enableExpires">Enable Expires</a> | <a
href="#expiresDefault">Expires Default</a> | <a
href="#expiresByType">Expires By
Type</a></p></section>
<section class="toc-row"><header><a
href="#geolocationDB">MaxMind GeoIP
DB</a></header><p>
<a href="#geoipDBFile">DB File Path</a> | <a
href="#geoipDBName">DB Name</a> | <a
href="#maxMindDBEnv">Environment
Variables</a></p></section>
<section class="toc-row"><header>IP2Location
DB</header><p>
<a href="#ip2locDBFile">IP2Location DB File Path</a>
| <a href="#ip2locDBCache">DB Cache
Type</a></p></section>
<section class="toc-row"><header>Using Apache
Configuration File</header><p>
<a href="#loadApacheConf">Load Apache
Configuration</a> | <a
href="#autoReloadApacheConf">Auto Reload On Changes</a>
| <a href="#apacheBinPath">Apache Binary Path</a> |
<a href="#apacheConfFile">Apache Configuration
File</a> | <a href="#apachePortOffset">Apache Port
Offset</a> | <a href="#apacheIpOffset">Apache IP
Offset</a> | <a href="#apacheHandledContent">Apache
Handled Content</a> | <a
href="#apacheIgnoredModules">Ignore Apache Modules</a> |
<a href="#jitConfig">Just In Time Configuration</a> |
<a href="#phpSuExec">PHP suEXEC</a> | <a
href="#phpSuExecMaxConn">PHP suEXEC Max Conn</a> | <a
href="#apacheEnableFP">Enable FrontPage Extension</a> |
<a href="#apacheEnvVars">Apache Environment
Variables</a></p></section>
<section class="toc-row"><header>Apache Style
Configuration</header><p>
<a href="#apacheConf">Apache Style
Configurations</a></p></section>
</section>
<section><div class="helpitem"><article
class="ls-helpitem"><div><header
id="serverName"><h3>Server Name<span
class="ls-permlink"><a
href="#serverName"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>A
unique name for this server. You can use $HOSTNAME as value.</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="lswsProcesses"><h3>Number of Processes<span
class="ls-permlink"><a
href="#lswsProcesses"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p><b>[Only
Available For Web Host Elite Licenses]</b> <br /> Specifies the
number of lshttpd workers. Enter 0 to have this number be decided
automatically.</p> <h4>Syntax</h4><p>Integer value
between 0 and 128.</p> <h4>Tips</h4><p><span
title="Performance"
class="ls-icon-performance"></span> Set an appropriate
number to suit your needs. Adding more processes may not necessarily mean
better performance.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="runningAs"><h3>Running As<span
class="ls-permlink"><a
href="#runningAs"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the user/group that the server process runs as. This value is set during
installation. In order to change it, you must download the installation
package and perform an upgrade via the command line.</p>
<h4>Apply</h4><p>Reinstall required.</p>
<h4>Tips</h4><p><span title="Security"
class="ls-icon-security"></span> Server should not be
run as a privileged user, such as "root". It is critical that the
server is configured to run as an un-privileged user/group combination that
does not have login/shell access. A user and group of <span
class="val">nobody</span> is generally a good
choice.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="serverPriority"><h3>Priority<span
class="ls-permlink"><a
href="#serverPriority"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
priority of the server processes. Value ranges from <span
class="val">-20</span> to <span
class="val">20</span>. A lower number means higher
priority.</p> <h4>Syntax</h4><p>Integer
number</p> <h4>Tips</h4><p><span
title="Performance"
class="ls-icon-performance"></span> Usually a higher
priority leads to slightly higher web performance on a busy server. Do not
set priority higher than that of database processes.</p>
<h4>See Also</h4><p
class="ls-text-small">External App <span
class="tagl"><a
href="ExtApp_Help.html#extAppPriority">Priority</a></span>,
<span class="tagl"><a
href="ServSecurity_Help.html#CGIPriority">CGI
Priority</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="cpuAffinity"><h3>CPU Affinity<span
class="ls-permlink"><a
href="#cpuAffinity"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>CPU
affinity binds a process to one or more CPUs (cores). It is beneficial for
a process to always use the same CPU because then the process can make use
of data left in CPU cache. If the process moves to a different CPU, there
is no use of CPU cache and unnecessary overhead is
required.<br/><br/> The CPU Affinity setting controls how many
CPUs (cores) one server process will be associated with. The minimum value
is <span class="val">0</span>, which will disable
this feature. The maximum value is the number of cores the server has.
Generally, <span class="val">1</span> is the best
setting because it creates the strictest use of CPU affinity and thus makes
the most use of CPU cache.<br/><br/> Default value: 0</p>
<h4>Syntax</h4><p>Integer value from 0 to 64. (0 will
disable this feature)</p>
<h4>Apply</h4><p>Reinstall required.</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="servChrootPath"><h3>Chroot Path<span
class="ls-permlink"><a
href="#servChrootPath"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p><span
class="tag">Enterprise Edition Only</span> Specifies the
directory where the chroot environment is rooted. Only "root"
user can run the server in chroot mode. Whether to run in chroot mode is
controlled by <span class="tagl"><a
href="#enableChroot">Enable chroot</a></span>
option. The installer program will set up the initial chroot environment
automatically. This entry is read-only, and if you want to change it,
please run the installer again from the command line.<br/><br/>
In the chroot environment, the server and its child processes cannot access
file systems outside of the chroot jail. Chroot is an advanced security
feature and additional administration may be required to make it work
properly. All required executables, libraries, configuration files, and
device files should be recreated within the chroot
jail.<br/><br/> As the root directory is changed, you need to
pay special attention to path configuration when an absolute path is used.
A Unix domain socket or swapping directory is always relative to the new
root directory. All other path configurations are always relative to the
real root.</p> <h4>Apply</h4><p>Reinstall
required.</p> <h4>Tips</h4><p><span
title="Security"
class="ls-icon-security"></span> Use chroot for better
security.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="enableChroot"><h3>Enable chroot<span
class="ls-permlink"><a
href="#enableChroot"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p><span
class="tag">Enterprise Edition Only</span> Specifies
whether to start the server in chroot mode. The new root directory is set
by <span class="tagl"><a
href="#servChrootPath">Chroot Path</a></span>
during installation.</p> <h4>Syntax</h4><p>Select
from radio box</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="enableLVE"><h3>Cloud-Linux<span
class="ls-permlink"><a
href="#enableLVE"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to enable CloudLinux's Lightweight Virtual Environment (LVE)
when it exists. You can use LiteSpeed with LVE to achieve better resource
management. For more information, please check <a
href="http://www.cloudlinux.com" target="_blank"
rel="noopener
noreferrer">http://www.cloudlinux.com</a>.</p>
<h4>Syntax</h4><p>Select from drop down list</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="inMemBufSize"><h3>Max I/O Buffer Size<span
class="ls-permlink"><a
href="#inMemBufSize"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the maximum buffer size that is used to store a request body and its
dynamically generated response. When this limit is reached, the server will
start to create temporary swapping files under <span
class="tagl"><a href="#swappingDir">Swapping
Directory</a></span>.</p>
<h4>Syntax</h4><p>Integer number</p>
<h4>Tips</h4><p><span title="Performance"
class="ls-icon-performance"></span> Set the buffer size
large enough to accommodate all concurrent requests/replies to avoid memory
to disk swapping. If there is frequent I/O activity to the swap directoy,
by default /tmp/lshttpd/swap/, this buffer size is too low and LiteSpeed is
swapping to disk.</p> <h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="#swappingDir">Swapping
Directory</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="swappingDir"><h3>Swapping Directory<span
class="ls-permlink"><a
href="#swappingDir"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the directory where the swapping files should be placed. When the server is
started in chroot mode, this directory is relative to the new root
directory, otherwise it is relative to the real root
directory.<br/><br/> The server uses its own virtual memory to
reduce system memory usage. Virtual memory and disk swapping are used to
store large request bodies and dynamically generated responses. The
swapping directory should be placed on a disk with enough
space.<br/><br/> Default value: /tmp/lshttpd/swap</p>
<h4>Syntax</h4><p>Absolute path</p>
<h4>Tips</h4><p><span title="Performance"
class="ls-icon-performance"></span> Place the swapping
directory on a separate disk or increase Max I/O Buffer Size to eliminate
swapping.</p> <h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="#inMemBufSize">Max I/O Buffer
Size</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoFix503"><h3>Auto Fix 503 Error<span
class="ls-permlink"><a
href="#autoFix503"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to try to fix the "503 Service Unavailable" error by
restarting the server gracefully. A "503" error is usually caused
by malfunctioning external applications and a web server restart can often
fix the error temporarily. If enabled, the server will restart
automatically whenever there are more than 30 "503" errors within
a 30 seconds span.<br/><br/> Default value: <span
class="val">No</span></p>
<h4>Syntax</h4><p>Select from radio box</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="enableh2c"><h3>Enable HTTP/2 Over Cleartext
TCP<span class="ls-permlink"><a
href="#enableh2c"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to enable HTTP/2 over non-encrypted TCP connections. Default is
disabled.</p> <h4>Syntax</h4><p>Select from radio
box</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="gracefulRestartTimeout"><h3>Graceful Restart Timeout
(secs)<span class="ls-permlink"><a
href="#gracefulRestartTimeout"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>During
a graceful restart, even after the new server instance is up, the old
instance will continue to handle existing requests. This timeout defines
how long the previous instance shall wait before exit. Default value is 300
seconds. -1 means wait forever. 0 means no wait and abort
immediately.</p> <h4>Syntax</h4><p>int</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="mime"><h3>MIME Settings<span
class="ls-permlink"><a
href="#mime"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the file that contains the MIME settings for this server. It is always
relative to the real root when an absolute path is given in chroot mode.
Click on the filename to view/edit the detailed MIME entries.</p>
<h4>Syntax</h4><p>Filename which can be an absolute path
or a relative path to $SERVER_ROOT.</p>
<h4>Tips</h4><p><span title="Information"
class="ls-icon-info"></span> Click the filename to edit
the MIME settings.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="mimesuffix"><h3>Suffixes<span
class="ls-permlink"><a
href="#mimesuffix"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>You
can list multiple suffixes for the same MIME type, using comma to
separate.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="mimetype"><h3>MIME Type<span
class="ls-permlink"><a
href="#mimetype"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>A
MIME type consists of a type and subtype in the format of
"type/subtype".</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="disableInitLogRotation"><h3>Disable Initial Log
Rotation<span class="ls-permlink"><a
href="#disableInitLogRotation"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to disable rotation of server error log file at startup. Initial
log rotation is enabled by default for standard installations. Servers
using cPanel, however, always write to the Apache error log and thus ignore
this setting.</p> <h4>Syntax</h4><p>Select from
radio box</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="showVersionNumber"><h3>Server Signature<span
class="ls-permlink"><a
href="#showVersionNumber"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to show the server signature and version number in the response
header's "Server" value. There are three options: when set
to <span class="val">Hide Version</span>, only
<span class="val">LiteSpeed</span> is shown. When set
to <span class="val">Show Version</span>, LiteSpeed
and the version number are shown. <span
class="tag">Enterprise Edition Only</span> When set to
<span class="val">Hide Full Header</span>, the entire
Server header will not be shown in the response header.</p>
<h4>Syntax</h4><p>Select from drop down list</p>
<h4>Tips</h4><p><span title="Security"
class="ls-icon-security"></span> Set to <span
class="val">Hide Version</span> if you do not wish to
expose the server version number.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="hideSigInErrorPage"><h3>Hide Error Page
Signature<span class="ls-permlink"><a
href="#hideSigInErrorPage"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether or not to show the lines <blockquote>Powered By
LiteSpeed.<br/> LiteSpeed Technologies is not responsible for
administration and contents of this web site!"</blockquote> on
your default error pages.</p>
<h4>Syntax</h4><p>Select from radio box</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="enableIpGeo"><h3>Enable GeoLocation Lookup<span
class="ls-permlink"><a
href="#enableIpGeo"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p><span
class="tag">Enterprise Edition Only</span> Specifies
whether to enable/disable IP Geolocation lookup. Can be set at server,
virtual host, or context level. IP Geolocation is disabled by default when
using value "Not Set".</p>
<h4>Syntax</h4><p>Select from radio box</p>
<h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="ServGeneral_Help.html#useIpInProxyHeader">Use Client IP
in Header</a></span>, <span class="tagl"><a
href="ServGeneral_Help.html#geoipDBFile">DB File
Path</a></span>,</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="useIpInProxyHeader"><h3>Use Client IP in
Header<span class="ls-permlink"><a
href="#useIpInProxyHeader"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to use the first most valid IP IP address listed in the
"X-Forwarded-For" HTTP request header for all IP address-related
features, including connection/bandwidth throttling, access control, and IP
geolocation.<br/><br/> This feature is useful if your web
server is behind a load balancer or a proxy server. If you select <span
class="val">Trusted IP Only</span>, then X-Forwarded-For
IP will be used only when the request is coming from trusted IPs defined in
the server-level <span class="tagl"><a
href="ServSecurity_Help.html#accessControl_allow">Allowed
List</a></span>.<br/><br/> <span
class="val">Keep Header from Trusted IP</span> is the
same as <span class="val">Trusted IP Only</span>, but
the X-Forwarded-For header used for the backend will not be modified to
include the connecting peer address.<br/><br/> <span
class="val">Use Last IP (for AWS ELB)</span> will use
the last IP address in the "X-Forwarded-For" list. Select this
option if you are using AWS Elastic Load Balancer or expect the real IP to
appended to the end of the "X-Forwarded-For" list.</p>
<h4>Syntax</h4><p>Select from drop down list</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="extAppAbort"><h3>External Application Abort<span
class="ls-permlink"><a
href="#extAppAbort"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>When
a client breaks a connection with the server, LiteSpeed Web Server can
automatically abort external application processes generating responses for
that client. Some users, however, may have (long-running) processes that
they wish to continue running whether or not the client is still
connected.<br/><br/> There are three options for
this:<br/> <ul> <li>No Abort: Never abort external
applications because of a broken connection.</li> <li>
Enable Abort for Requests from External IPs: Only processes started by
requests from external IPs will be automatically aborted because of a
broken connection. This is the default setting. It is a good setting if you
have some internal long-running processes, like some cron jobs.
</li> <li> Enable Abort for All Requests: External
application processes will be automatically aborted if the connection is
broken, regardless of the source of the request. </li>
</ul></p> <h4>Syntax</h4><p>Select from drop
down list</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoUpdateInterval"><h3>Check For Update<span
class="ls-permlink"><a
href="#autoUpdateInterval"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
how often the update agent will check for a new product release. Options
are "Daily", "Weekly", "Monthly" and
"Disable".</p> <h4>Syntax</h4><p>Select
from drop down list</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoUpdateDownloadPkg"><h3>Download Updates<span
class="ls-permlink"><a
href="#autoUpdateDownloadPkg"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to auto-download a new product release package file when available.
If a new package has been successfully downloaded, an online one-click
upgrade can be performed via the WebAdmin console under Service Manager -
<span class="tagl"><a
href="ServerStat_Help.html#vermgr">Version
Management</a></span>.</p>
<h4>Syntax</h4><p>Select from drop down list</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="adminEmails"><h3>Administrator Email<span
class="ls-permlink"><a
href="#adminEmails"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the server administrator's email address(es). If specified,
administrators will be notified by email of important events (for example,
when the LiteSpeed service is restarted automatically due to crash
detection or when license is expiring).</p>
<h4>Syntax</h4><p>Comma delimited list of email
address.</p> <h4>Tips</h4><p><span
title="Information"
class="ls-icon-info"></span> Email alert feature will
only work if the server has an active MX server such as postfix, exim, or
sendmail.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="indexFiles"><h3>Index Files<span
class="ls-permlink"><a
href="#indexFiles"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
names of index files that will be searched sequentially when a URL is
mapped to a directory. You can customize it at the server, virtual host,
and context level.</p>
<h4>Syntax</h4><p>Comma-delimited list of index
filenames.</p> <h4>Tips</h4><p><span
title="Performance"
class="ls-icon-performance"></span> Only set index files
that you need.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoIndex"><h3>Auto Index<span
class="ls-permlink"><a
href="#autoIndex"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to generate a directory index on the fly when index files listed in
<span class="tagl"><a
href="#indexFiles">Index Files</a></span> are not
available in a directory. This option is customizable at the virtual host
and context level, and is inherited along the directory tree until it is
explicitly overridden. You can customize the generated index page. Please
check online wiki How-tos.</p>
<h4>Syntax</h4><p>Select from radio box</p>
<h4>Tips</h4><p><span title="Security"
class="ls-icon-security"></span> It is recommended to
turn off Auto Index wherever possible to prevent revealing confidential
data.</p> <h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="#indexFiles">Index Files</a></span>,
<span class="tagl"><a
href="#autoIndexURI">Auto Index
URI</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoIndexURI"><h3>Auto Index URI<span
class="ls-permlink"><a
href="#autoIndexURI"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the URI that will be used to generate the index page when index files
listed in <span class="tagl"><a
href="#indexFiles">Index Files</a></span> are not
available in a directory. LiteSpeed web server uses an external script to
generate the index page providing the maximum customization flexibility.
The default script produces an index page with same look as Apache's.
To customize the generated index page, please read online wiki How-tos. The
directory to be indexed is passed to the script via an environment variable
"LS_AI_PATH".</p>
<h4>Syntax</h4><p>URI</p> <h4>See
Also</h4><p class="ls-text-small"><span
class="tagl"><a href="#indexFiles">Index
Files</a></span>, <span class="tagl"><a
href="#autoIndex">Auto Index</a></span></p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="htaccess"><h3>HT Access<span
class="ls-permlink"><a
href="#htaccess"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>The
following directives are supported in a directory level access control file
(.htaccess file).<br/> <ul> <li> Authentication
<ul> <li>AuthGroupFile</li>
<li>AuthName</li> <li>AuthType</li>
<li>AuthUserFile</li> <li>Require</li>
<li>Satisfy</li> <li><Limit> (GET,
HEAD, POST only)</li> <li><LimitExcept>
(GET, HEAD, POST only)</li> </ul> </li>
<li> Access Control <ul>
<li>Allow</li> <li>Deny</li>
<li>Order</li> <li><Limit> (GET,
HEAD, POST only)</li> <li><LimitExcept>
(GET, HEAD, POST only)</li> </ul> </li>
<li> File Info <ul>
<li>AddDefaultCharset</li> <li>AddType</li>
<li>DefaultType</li> <li>ForceType</li>
<li>Redirect</li>
<li>RedirectPermanent</li>
<li>RedirectTemp</li> <li>RewriteBase</li>
<li>RewriteCond</li>
<li>RewriteEngine</li>
<li>RewriteOptions</li> <li>RewriteRule</li>
</ul> </li> <li> Other <ul>
<li>DirectoryIndex</li>
<li>ExpiresActive</li> <li>ExpiresByType</li>
<li>ExpiresDefault</li>
<li>Options</li> </ul> </li>
</ul></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="allowOverride"><h3>Allow Override<span
class="ls-permlink"><a
href="#allowOverride"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
what directives in an access control file are allowed. An access control
file can be placed in a directory to control the accessibility of files
under that directory.<br/> <ul> <li>When nothing is
checked, inherited default settings will be used.</li>
<li>When <span class="val">None</span> is
checked, access control files will be ignored.</li> <li>
When <span class="val">Limit</span> is checked,
directives "Allow", "Deny", and "Order" are
allowed. <Limit> and <LimitExcept>
directives are also allowed with limited support for GET, HEAD, and POST
requests. </li> <li> When <span
class="val">Auth</span> is checked, directives
"AuthGroupFile", "AuthName", "AuthType",
"AuthUserFile", "Require", and "Satisfy"
are allowed. <Limit> and <LimitExcept>
directives are also allowed with limited support for GET, HEAD, and
POST requests. </li> <li> When <span
class="val">FileInfo</span> is checked, directives
"AddDefaultCharset", "AddType",
"DefaultType", "ForceType", "Redirect",
"RedirectPermanent", "RedirectTemp",
"RewriteBase", "RewriteCond",
"RewriteEngine", "RewriteOptions", and
"RewriteRule" are allowed. </li> <li> When
<span class="val">Indexes</span> is checked,
directives "DirectoryIndex", "ExpiresActive",
"ExpiresByType", and "ExpiresDefault" are allowed.
</li> <li>When <span
class="val">Options</span> is checked, directive
"Options" is allowed.</li> </ul><br/> Allow
Override configuration is available at the Server, Virtual Host, and
Context levels. If a configuration is unchecked at the Server level, those
controlled directives will be disabled for the entire server regardless of
settings at lower levels. Lower levels can disable a setting that is
enabled at a higher level, but cannot enable a setting that is disabled at
an upper level.<br/><br/> Default values:<br/>
<b>Server level:</b> "None" (ignore access control
file)<br/> <b>VH level:</b> Inherit Server level
setting<br/> <b>Context level</b> Inherit VH level
setting</p> <h4>Syntax</h4><p>Select from
checkbox</p> <h4>Tips</h4><p><span
title="Performance"
class="ls-icon-performance"></span> If there is no need
for directory level configuration customization, check <span
class="val">None</span>.</p> </article>
</div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="accessFileName"><h3>Access File Name<span
class="ls-permlink"><a
href="#accessFileName"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the name of access control files. These files will be used only if <span
class="tagl"><a href="#allowOverride">Allow
Override</a></span> is enabled. Default name is <span
class="val">.htaccess</span>. You can configure this at
server level and virtual host level. Server level is the default setting,
and you can override it at virtual host level.</p>
<h4>Syntax</h4><p>Filename starting with
"."</p> <h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="#allowOverride">Allow
Override</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="enableExpires"><h3>Enable Expires<span
class="ls-permlink"><a
href="#enableExpires"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to generate an Expires header for static files. If enabled, an
Expires header will be generated based on <span
class="tagl"><a href="#expiresDefault">Expires
Default</a></span> and <span class="tagl"><a
href="#expiresByType">Expires By
Type</a></span>.<br/><br/> This can be set at
server, virtual host and context level. Lower level settings will override
higher level ones, i.e. context settings will override virtual host
settings and virtual host settings will override server settings.</p>
<h4>Syntax</h4><p>Select from radio box</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="expiresDefault"><h3>Expires Default<span
class="ls-permlink"><a
href="#expiresDefault"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
default settings for Expires header generation. This setting takes effect
when <span class="tagl"><a
href="#enableExpires">Enable Expires</a></span> is
set to "Yes". It can be overridden by <span
class="tagl"><a href="#expiresByType">Expires
By Type</a></span>. Do not set this default at the server or
virtual host level unless you have to, since it will generate Expires
headers for all pages. Most of time this should be set at the context level
for certain directories that do not change often. If there is no default
setting, no Expires header will be generated for types not specified in
<span class="tagl"><a
href="#expiresByType">Expires By
Type</a></span>.</p>
<h4>Syntax</h4><p>A|Mseconds<br/> The file will
expire after base time(A|M) plus specified seconds. Base time "A"
sets the value to the client's access time and "M" to the
file's last modified time.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="expiresByType"><h3>Expires By Type<span
class="ls-permlink"><a
href="#expiresByType"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
Expires header settings for individual MIME types.</p>
<h4>Syntax</h4><p>Comma delimited list of
"MIME-type=A|Mseconds". The file will expire after base time
(A|M) plus specified seconds.<br/><br/> Base time "A"
sets the value to the client's access time and "M" to the
file's last modified time. MIME-type accepts wildcard "*",
like image/*.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="geolocationDB"><h3>MaxMind GeoIP DB<span
class="ls-permlink"><a
href="#geolocationDB"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Multiple
MaxMind geolocation databases can be specified here. MaxMind has the
following type of DBs: Country, Region, City, Organization, ISP and
Netspeed. If multiple databases of types "Country",
"Region", and "City" are configured, the last
configuration will be effective.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="geoipDBFile"><h3>DB File Path<span
class="ls-permlink"><a
href="#geoipDBFile"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the path to MaxMind GeoIP database.</p>
<h4>Syntax</h4><p>Absolute path</p>
<h4>Example</h4><div
class="ls-example">/usr/local/share/GeoIP/GeoLite2-Country.mmdb</div></article>
</div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="geoipDBName"><h3>DB Name<span
class="ls-permlink"><a
href="#geoipDBName"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>MaxMind
GeoIP database name. As of GeoIP2, this setting is
required.<br/><br/> When upgrading from a GeoIP to a GeoIP2,
using values "COUNTRY_DB", "CITY_DB", or
"ASN_DB" for this setting will automatically populate PHP's
$_SERVER variable with some GeoIP compatible entries (listed by DB Name
value below) to help ease this transition.<br/><br/>
<b>CITY_DB:</b> 'GEOIP_COUNTRY_CODE',
'GEOIP_COUNTRY_NAME', 'GEOIP_CONTINENT_CODE',
'GEOIP_COUNTRY_CONTINENT', 'GEOIP_DMA_CODE',
'GEOIP_METRO_CODE', 'GEOIP_LATITUDE',
'GEOIP_LONGITUDE', 'GEOIP_POSTAL_CODE', and
'GEOIP_CITY'.<br/> <b>COUNTRY_DB:</b>
'GEOIP_COUNTRY_CODE', 'GEOIP_COUNTRY_NAME',
'GEOIP_CONTINENT_CODE', and
'GEOIP_COUNTRY_CONTINENT'.<br/> <b>ASN_DB:</b>
'GEOIP_ORGANIZATION' and 'GEOIP_ISP'.</p>
<h4>Example</h4><div
class="ls-example">COUNTRY_DB</div></article>
</div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="maxMindDBEnv"><h3>Environment Variables<span
class="ls-permlink"><a
href="#maxMindDBEnv"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Assign
the results of database lookups to environment variables.</p>
<h4>Syntax</h4><p>Variable_Name
mapped_DB_data<br/><br/> One entry per line. Path to data can
use map keys or 0-based array indexes, both being separated by /.</p>
<h4>Example</h4><div
class="ls-example">COUNTRY_CODE
COUNTRY_DB/country/iso_code<br/> REGION_CODE
CITY_DB/subdivisions/0/iso_code</div></article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="ip2locDBFile"><h3>IP2Location DB File Path<span
class="ls-permlink"><a
href="#ip2locDBFile"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>The
location of a valid database file.</p>
<h4>Syntax</h4><p>Filename which can be an absolute path
or a relative path to $SERVER_ROOT.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="ip2locDBCache"><h3>DB Cache Type<span
class="ls-permlink"><a
href="#ip2locDBCache"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>The
caching method used. The default value is <span
class="val">Memory</span>.</p>
<h4>Syntax</h4><p>Select from drop down list</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="loadApacheConf"><h3>Load Apache
Configuration<span class="ls-permlink"><a
href="#loadApacheConf"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether LiteSpeed will read and use a Apache configuration file to
configure the web server. Native configurations will have higher priority
when there is conflict between LiteSpeed internal and Apache-based
configurations.</p> <h4>Syntax</h4><p>Select from
radio box</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="autoReloadApacheConf"><h3>Auto Reload On
Changes<span class="ls-permlink"><a
href="#autoReloadApacheConf"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
how to apply Apache configuration changes. When set to "Yes",
LSWS will perform a graceful restart whenever the Apache configuration file
has been modified. This may cause LSWS to restart multiple times when
updating Apache configurations. A better solution (introduced in version
3.3.8) is "Use Apache binary wrapper". This will replace Apache
httpd binary with a wrapper script. Whenever Apache is requested to
start/stop/restart, the script will tell LSWS to take corresponding action.
<span class="tagl"><a
href="#apacheBinPath">Apache Binary
Path</a></span> must be set to use this setting. Default is
"No" for standard installations. For cPanel servers, the default
is "Use Apache binary wrapper". ("Override cPanel restart
HTTPD script" is an optional workaround that should only be used if
the option "Use Apache binary wrapper" is having problems.) For
other control panels default is "Yes".</p>
<h4>Syntax</h4><p>Select from radio box</p>
<h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="#apacheBinPath">Apache Binary
Path</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheBinPath"><h3>Apache Binary Path<span
class="ls-permlink"><a
href="#apacheBinPath"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the location of the Apache binary. Usually, it is located at
/usr/local/apache/bin/httpd or /usr/local/apache2/bin/httpd, etc. This
option must be set when "Use Apache binary wrapper" is used for
<span class="tagl"><a
href="#autoReloadApacheConf">Auto Reload On
Changes</a></span>.</p> <h4>See
Also</h4><p class="ls-text-small"><span
class="tagl"><a
href="#autoReloadApacheConf">Auto Reload On
Changes</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheConfFile"><h3>Apache Configuration
File<span class="ls-permlink"><a
href="#apacheConfFile"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the location of Apache configuration file. Usually, it is located at
/usr/local/apache/conf/httpd.conf or /etc/httpd/conf/httpd.conf.</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apachePortOffset"><h3>Apache Port Offset<span
class="ls-permlink"><a
href="#apachePortOffset"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
an offset to be added to listening TCP ports specified in the Apache
configuration file. In the testing phase, this allows LiteSpeed to run
alongside Apache on a different port instead of switching back and forth
between LiteSpeed and Apache on a production server.<br/> If set to
<span class="val">0</span> or not set, LiteSpeed will
use the ports specified in the Apache configuration file. When testing,
make this setting a non-zero value. LiteSpeed will then add this offset
value to the port specified in the Apache configuration and use this port.
After confirming that everything works properly, you can stop Apache, set
this option back to <span class="val">0</span>, and
restart LiteSpeed.</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheIpOffset"><h3>Apache IP Offset<span
class="ls-permlink"><a
href="#apacheIpOffset"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
an offset to be added to listening IP address specified in the Apache
configuration file. This allows LiteSpeed to run alongside Apache in the
testing phase instead of switching back and forth between LiteSpeed and
Apache on a production server. The calculated IP address has to be
available on this server.</p> <h4>Syntax</h4><p>The
offset should be set as an integer (allow negative number), not an IP
address. Adding "256" will add 1 to the value of the C class
subnet. This option only works with IPv4 address.</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheHandledContent"><h3>Apache Handled
Content<span class="ls-permlink"><a
href="#apacheHandledContent"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
resources to be passed to and processed by Apache on the backend. This
feature requires running Apache parallel to LiteSpeed on either another IP
or a different port, so either "Apache Port Offset" or
"Apache IP Offset" should be set to a non-zero value.</p>
<h4>Syntax</h4><p>Resources are specified by a comma
delimited list of URI, file suffixes, or regular expressions. A URI starts
with "/"; a suffix starts with ".", a regular
expression starts with "exp:". For example: "/svn/,
.shtml" lets Apache handle requests with a URI starting with
"/svn/" or ending with ".shtml". The same effect can be
achieved with the regular expression "exp:^/svn/,
exp:\.shtml$".</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheIgnoredModules"><h3>Ignore Apache
Modules<span class="ls-permlink"><a
href="#apacheIgnoredModules"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
a list of names of Apache modules that should be ignored by LiteSpeed while
parsing the Apache configuration file. LiteSpeed will treat the listed
modules as unsupported. This will cause configuration directives related to
these modules enclosed in matching <IfModule> or
<IfDefined> tags to be ignored.</p>
<h4>Syntax</h4><p>comma delimited list of module
names</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="jitConfig"><h3>Just In Time Configuration<span
class="ls-permlink"><a
href="#jitConfig"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>With
just in time configuration, the web server only finalizes vhost
configurations when that virtual host is accessed for the first time,
instead of loading all configurations at start up. This allows the web
server to save memory and speed up server start up.</p>
<h4>Syntax</h4><p>Select from radio box</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="phpSuExec"><h3>PHP suEXEC<span
class="ls-permlink"><a
href="#phpSuExec"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to run PHP script in suEXEC mode when "user" and
"group" are specified for a virtual host. When set to <span
class="val">Yes</span>, PHP scripts will be executed
under the user (and group unless <span class="tagl"><a
href="ServSecurity_Help.html#forceGID">Force
GID</a></span> is set) specified. When set to <span
class="val">User's Home Directory Only</span>,
scripts outside a user's home directory will run as the global
user/group that the web server run as. When using DirectAdmin, <span
class="val">User's Home Directory Only</span> is
recommended. Default is <span
class="val">No</span>.</p>
<h4>Syntax</h4><p>Select from radio box</p>
<h4>See Also</h4><p
class="ls-text-small"><span class="tagl"><a
href="ServSecurity_Help.html#forceGID">Force
GID</a></span></p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="phpSuExecMaxConn"><h3>PHP suEXEC Max Conn<span
class="ls-permlink"><a
href="#phpSuExecMaxConn"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
the maximum number of concurrent PHP processes that can be created by LSWS
for each user when running PHP scripts in suEXEC mode. Default value is
<span class="val">5</span>.</p>
<h4>Syntax</h4><p>Integer number</p>
<h4>Tips</h4><p><span title="Information"
class="ls-icon-info"></span> This limit is per user per
lshttpd process. Thus, if you have a 2-CPU license, this limit will be
doubled. The limit will be 4x for a 4-CPU license, and so on.</p>
</article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheEnableFP"><h3>Enable FrontPage
Extension<span class="ls-permlink"><a
href="#apacheEnableFP"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
whether to explicitly enable Microsoft Front Page Server Extension or not.
Usually, LSWS will enable it when module "frontpage" has been
loaded in Apache httpd.conf. However, when mod_frontpage is statically
linked into the Apache binary, configuration for the FrontPage module is
not in httpd.conf, and you need to enable it explicitly here. Default is
"disabled".</p> <h4>Syntax</h4><p>Select
from radio box</p> </article> </div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheEnvVars"><h3>Apache Environment
Variables<span class="ls-permlink"><a
href="#apacheEnvVars"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>For
shell environment variables used inside the Apache configuration file, LSWS
will replace "${ENVVAR}" with the values set here. If the ENVVAR
variable is not set here, "${ENVVAR}" occurrences are left
unchanged.</p> <h4>Syntax</h4><p>Name and value
pairs, one pair per line in the form of ENV=VALUE</p> <h4>See
Also</h4><p class="ls-text-small">Apache Env Syntax
<a
href="http://httpd.apache.org/docs/current/configuring.html#syntax"
target="_blank" rel="noopener
noreferrer">reference</a></p> </article>
</div>
<div class="helpitem"><article
class="ls-helpitem"><div><header
id="apacheConf"><h3>Apache Style Configurations<span
class="ls-permlink"><a
href="#apacheConf"></a></span><span
class="top"><a
href="#top">⇑</a></span></h3></header></div><h4>Description</h4><p>Specifies
Apache configuration directives (supported by LiteSpeed) that you want to
use in LiteSpeed native configuration file. For example, to override the
default PHP configurations (php.ini entries) the server will need four
directives: "php_value", "php_flag",
"php_admin_value" and "php_admin_flag".</p>
<h4>Syntax</h4><p>Same as Apache configuration
file.</p> </article> </div>
</section>
</article><div class="ls-col-1-1"><footer
class="copyright">Copyright © 2003-2020. <a
href="https://www.litespeedtech.com">LiteSpeed Technologies
Inc.</a> All rights reserved.</footer>
</div></div>
</body>
</html>