LiteSpeed

Author: wpuser

  • Setting Up Multiple PHP Versions

    Setting Up Multiple PHP Versions

    Here at LiteSpeed, we are in the midst of a major overhaul of our documentation. It’s a lot of hard work — like carving granite with tweezers — but we don’t want to make you wait till it’s finished to get some of the benefits. So, on the blog, we will be sharing tips about how you can make LSWS run better for you. Today’s post is an overview of setting up multiple PHP versions when you use a control panel (though it will work if you don’t use a control panel as well). (more…)

  • A Message from Our Friends at InterServer

    A Message from Our Friends at InterServer

    InterServer recently posted a piece on their blog detailing our long history together. (more…)

  • Trouble Shooting: “PECL Install Doesn’t Work”

    Trouble Shooting: “PECL Install Doesn’t Work”

    Some users prefer to mount their /tmp directory as noexec for security reasons, but we’ve seen that this can cause a problem for PECL installs. Pointing the PECL temp_dir to a new path gets around this problem. (more…)

  • So Many Licenses… Which One Is Right For Me?

    So Many Licenses… Which One Is Right For Me?

    Updated November 2019. 

    We get a lot of questions about licenses, especially which license is best for a particular customer. I want to take a moment to answer some of the most frequent questions/misunderstandings about LiteSpeed licenses: (more…)

  • We Update Constantly (or Why Our Build Numbers Are Only Three Digits)

    We Update Constantly (or Why Our Build Numbers Are Only Three Digits)

    Often times, when you have a problem with LSWS, one of our staff will suggest that you update to the latest version of the web server. “But I am using the latest version,” you say. “No,” the staff member says, “we updated it yesterday.”

    This is something we get asked about quite often: Why don’t we add another digit to distinguish between builds whenever we update LSWS? The reason is that we update it so often — and for so many configuration-specific bugs — that for you, the user, to try to keep up with these updates is an exercise in futility. (more…)

  • Web Performance and the Bottom Line Pt. 2

    Web Performance and the Bottom Line Pt. 2

    Yesterday, I linked to a Varnish blog post talking about the effect of page upload time on business. Today I came across a post on the Simple Helix blog I like even more. (more…)

  • “Web Performance and the Bottom Line” (An External Link)

    “Web Performance and the Bottom Line” (An External Link)

    Here’s a post from the Varnish Software blog discussing how web site speed affects online businesses. One of the studies they use is four years old, but I think the numbers they show beautifully illustrate why speed matters: (more…)

  • PHP Selector (from CloudLinux)

    PHP Selector (from CloudLinux)

    Recently, CloudLinux has added support for LSWS to its PHP Selector. PHP Selector allows the end-user to select their PHP version and what PHP modules they want to run. (more…)

  • New Faces and a New Base

    New Faces and a New Base

    We’re not sure if you’ve noticed, but LiteSpeed has been expanding. (more…)

  • Closing the Loopholes: Disable CGI Override

    Closing the Loopholes: Disable CGI Override

    Many of our customers disable CGI on their servers because of the risks involved with running CGI: Poorly written CGI scripts can broadcast all kinds of sensitive information to the world. If a hacker, creeping in through a tiny security hole, can successfully upload a CGI script and make it work, they can get access (and even root access) to your server without much restriction. Or the hacker could be one of your clients (signed up with a stolen credit card, perhaps), and then s/he doesn’t need a security hole to run a malicious CGI script.

    There are definitely risks, but many web servers don’t give you a good way to neutralize them. On Apache, you can disable CGI in WHM by unchecking the ExecCGI box (Service Configuration > Apache Configuration > Global Configuration). Disabling CGI, though, does not mean that it stays disabled. Users can enable it using the Options directive Options +ExecCGI in a .htaccess file. (You could turn off the Options directive, but there are many legitimate uses as well — the index feature, for example.)

    This is why LiteSpeed has developed the Apache-style server-level configuration directive DisableCGIOverride. The Disable CGI Overrride directive makes it impossible for users to turn on or off CGI through .htaccess. It will keep that CGI on/off switch firmly where you left it. (If, for some reason, you don’t want any users to turn off CGI, this directive will keep it on.) For cPanel users, just paste the following directive into one of the includes in the Include Editor (Service Configuration > Apache Configuration > Include Editor) in WHM:

    <IfModule LiteSpeed>
DisableCgiOverride On
</IfModule>

    When the Disable CGI Override directive is On, users cannot enable or disable CGI.

    More safety, more control, yet another reason to choose LiteSpeed.