Just In Time Configuration. Enable FrontPage Extension. Apache Environment Variables. Apache Style Configurations. Description: A unique name for this server. This value was set during installation. To change it, you have to download the installation package and perform an upgrade via command line. Apply: Reinstall required.
Tips: [Security] Server should not run as a privileged user such as "root". Description: Specifies priority of the server processes. Value ranges from to A lower number means higher priority. Tips: [Performance] Usually a higher priority leads to slightly higher web performance on a busy server. Do not set priority higher than that of database processes.
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. The minimum value is 0 , which is the default value and will disable this feature. The maximum value is the number of cores the server has. Generally, 1 is the best setting because because it creates the strictest use of CPU affinity and thus makes the most use of CPU cache.
Syntax: Integer value from 1 to the number of cores the server has. Description: Enterprise Edition Only 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 Enable chroot 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. 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.
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. Tips: [security] Use chroot for better security. Description: Enterprise Edition Only Specifies whether to start the server in chroot mode.
The new root directory is set by Chroot Path during installation. Description: 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 Swapping Directory.
See Also: Swapping Directory. Description: 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. 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. Description: Specifies whether to try to fix the " Service Unavailable" error by restarting the server gracefully. A "" 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 "" errors within a 30 seconds span.
This feature is enabled by default. Default is disabled. Description: 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 seconds.
It is always relative to the real root when an absolute path is given in chroot mode. Description: 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. Description: Specifies whether to show the server signature and version number in the response header's "Server" value.
There are three options: when set to Hide Version , only LiteSpeed is shown. When set to Show Version , LiteSpeed and the version number are shown. Tips: [Security] Set to Hide Version if you do not wish to expose the server version number. LiteSpeed Technologies is not responsible for administration and contents of this web site!
It can be set at server-, virtual host-, or context-level. IP Geolocation is disabled by default when using value "Not Set". This feature is useful if your web server is behind a load balancer or a proxy server. Description: 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. There are three options for this: No Abort: Never abort external applications because of a broken connection.
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. Enable Abort for All Requests: External application processes will be automatically aborted if the connection is broken, regardless of the source of the request. Description: Specifies how often the update agent will check for a new product release.
Options are "Daily", "Weekly", and "Monthly". Description: 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 - Version Management. Description: 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. Tips: Email alert feature will only work if the server has an active MX server such as postfix, exim, or sendmail. Description: 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. Description: Specifies whether to generate a directory index on the fly when index files listed in Index Files 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. Tips: [Security] It is recommended to turn off Auto Index wherever possible to prevent revealing confidential data. Description: Specifies the URI that will be used to generate the index page when index files listed in Index Files are not available in a directory.
You can also configure LSWS to read your existing Apache configuration if you have a working Apache server running without a control panel. In these scenarios, users may continue to set up everything in Apache, the same way as before.
Sometimes, users may run LSWS natively without a control panel. Please see Quick Reference for All Commands. LiteSpeed is a drop-in replacement in a control panel environment, which means that LiteSpeed can read Apache configuration files and run LSWS based on Apache's settings.
LiteSpeed's implementation of Apache functionality includes but is not limited to the following Apache modules. This list is gradually expanding as new feature requests are implemented:. LiteSpeed Web Server also uses the same syntax as Apache for distributed configuration file. Custom templates can be used to make LSWS virtual hosts, and simultaneously prepare them for popular web applications and plugins.
All templates use LiteSpeed native configurations. Templates are unnecessary if you are migrating an existing site with web applications from Apache. Edit this page Backlinks. Configuration How-Tos This section of the wiki provides articles on configuring LiteSpeed Web Server to achieve desired functionality, better performance, or security. Maxmind database support for GeoIP2 lookup. Brotli compression for dynamic responses and automatic gzip and brotli conversion for cached pages. Improved cache engine to fix bad cache storage directory and file permissions.
Improve rewrite Engine to match Apache behavior. How to improve site performance. How to resolve high server load issue. How to control the number of connections your PHP engine can serve at once. How QUIC makes the web quicker. How to enable the PageSpeed module. How to enable GeoLocation. How to enable IP2Location. OLS gets all server and virtual host configurations through this main file.
Technically, you can use include files in the OLS configuration, however this is not currently supported by the WebAdmin Console. Support for include files is coming to WebAdmin in the future, but until is does, if you intend to use include files, then you must edit the configuration via text editor.
Features Install Support Forum. You are here:. Posted September 4,
0コメント