Litespeed Httpd

Posted : admin On 15.08.2021

OpenLiteSpeed Configuration Examples

Litespeed Web Server. Litespeed is a lightweight web server that is developed and owned by the company Litespeed Technologies. Litespeed web server again replaces Apache webserver. But Litespeed is highly compatible with all Apache Modules like modsecurity, modrewrite etc. Litespeed web server has three releases. LiteSpeed is the first to provide a production-ready implementation of this new Internet protocol, previously known as HTTP-over-QUIC. Learn more about HTTP/3 and LiteSpeed's pioneering efforts here! Compare LiteSpeed to Apache and nginx Looking for a new web server? LiteSpeed Web Server was built from the ground up to encorporate the best of both worlds: an event-driven architecture like nginx, and Apache.htaccess compatibility. Being event-driven, LiteSpeed Web Server consumes fewer resources than Apache's process-based model, leading to better performance. Litespeed Technologies Litespeed Web Server security vulnerabilities, exploits, metasploit modules, vulnerability statistics and list of versions (e.g.: CVE-2009-1234 or 2010-1234 or 20101234) Log In Register.

You can install OpenLiteSpeed in multiple ways, and each way may associate OLS configuration files in different locations. The purpose of this article is not to cover the various default configurations for different installation methods, but instead to show you some basic OLS configuration example files to give you a good starting point for a new server. We are assuming that you download the package from the website and install from the package (binary install).

Server Root

Normally the default OLS server root is /usr/local/lsws. Almost all default files for OLS will be under the server root. Of course, for newly created virtual hosts, you are free to use /home/user1/, /home/user2/, etc. for the virtual host root.

Main Configuration File

The most important configuration files are located in /usr/local/lsws/conf/, with httpd_config.conf being the main OLS configuration. Here’s an example of the contents of that file:

Virtual Host Configuration Files

Under /usr/local/lsws/conf/vhosts/, you will find a configuration file for each virtual host. /usr/local/lsws/conf/vhosts/Example/vhconf.conf is an example vhost configuration file which contains the following:

Editing Configuration Files

The best and easiest way to edit the OpenLiteSpeed configuration is through the WebAdmin Console. When using WebAdmin, there is no need for you to remember OLS configuration syntax, and it is much easier for a beginner with no prior knowledge of OpenLiteSpeed. OLS configuration files are plain text. If you are an advanced OLS user and know OLS syntax, then you are certainly encouraged to use vi to edit the configuration file directly. Don’t forget to restart OLS after any changes to the configuration.

Include Files

Normally the main OLS configuration file httpd_config.conf defines different virtual host configuration file locations. 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.

Alternately, you may take advantage of DirectAdmin’s OpenLiteSpeed support, which does split OLS configurations into different include files.

You can customize OpenLiteSpeed Virtual Host configuration in DirectAdmin. Despite the misleading name, Custom HTTPd Configurations on the DA Console may be used to add, modify, or edit an OLS virtual host configuration, when OLS is running. The customized changes you make will not be overwitten the next time DA CustomBuild is run to upgrade OLS.

When you place code in *Custom HTTPd Configuration*, files are created in /usr/local/directadmin/data/users/$USER/domains/*. These code blocks are always inserted into /usr/local/directadmin/data/users/$USER/openlitespeed.conf, and should not be edited directly, as DirectAdmin updates will overwrite any changes.

To get started, navigate to DirectAdmin Control Panel > Server Manager > Custom HTTPD Configurations. Select openlitespeed.conf for the virtual host to be modified (in this case, da-ols):

The OLS virtual host configuration will be displayed. Click the CUSTOMIZE button to edit it, and save when you’re finished.

As an example, if you’d like to define a customized 404 error page for that domain, you would add this content to the text box:


Remote play ps4 dualshock 4 pro. CUSTOM1: Appears at the very top of the template, before setting the variables.

CUSTOM2: Appears in scripthandler{} section.

CUSTOM3: Appears in ALL context{} sections, used for password protected directories.

CUSTOM4: Appears in phpIniOverride{} section.

CUSTOM5: Appears in rewrite{} section.

Litespeed Httpd Vulnerabilities

CUSTOM6: Appears in vhssl{} section.

CUSTOM7: The very last entry.


After saving, you will see a /usr/local/directadmin/data/users/$USER/domains/ file created with the following content:

Litespeed Httpd.conf

The new content will also have been inserted into /usr/local/directadmin/data/users/$USER/openlitespeed.conf.