Projects / LiteSpeed Web Server

LiteSpeed Web Server

LiteSpeed Web Server is a high-performance, secure, easy-to-use, and Apache interchangeable Web server. It supports HTTP/1.1, SSL, CGI, FastCGI, LSAPI, PHP, JSP, Servlets, GZIP compression, chroot, IP level throttling, connection accounting, DoS attack prevention, and instant recovery mechanisms. With its Apache compatible rewrite engine, .htaccess, and MS FrontPage support, migration is quick and easy. A Web interface is included for administration and configuration. It can be used as a content accelerator, compression proxy, or a security guard running in front of any Web and application server.

Tags
Licenses
Operating Systems
Implementation

RSS Recent releases

Release Notes: SSL client authentication has been added. A GUI interface for building PHP has been added to the Web console. The process manager for PHP suEXEC has been improved. Compatibility with control panels has been greatly improved. The installer has been improved to include default configuration for using with hosting control panels. Support for vmware/XEN/UserModeLinux VPS has been added for the VPS license. The security of the directory autoindex has been enhanced, and there are many minor bugfixes and improvements.

  •  22 Oct 2007 13:21

Release Notes: A security flaw that may have exposed PHP source code has been fixed.

  •  05 Sep 2007 15:27

Release Notes: The default Rails vhost template has been updated with Rails page cache support. User managed LiteSpeed Rails configuration has been improved to work properly with subdomain configuration. YUI has been replaced with a light-weight library in the Web admin console. A bug in handling CGI command line parameters has been fixed. The performance of the rewrite engine has been improved for complex rewrite rules. The rewrite rule parser has been improved to ignore trailing comments. The size limit of XML elements in the litespeed configuration file has been increased. The graceful restart procedure has been improved.

Release Notes: Compatibilities with the plesk control panel has been improved. Gzip compression support has been improved to store each compressed static file in its own cache directory. The REDIRECT_URL and REDIRECT_QUERY_STRING environment variables have been added. Directory redirection has been improved to give better support for the RESTful route of Ruby On Rails. Directory auto index has been improved. The i-node value in ETag can be turned off. A bug in the security engine has been fixed. Restarting of individual virtual hosts can be managed by the user with a simple configuration file.

  •  02 May 2007 10:51

Release Notes: The request rate throttling algorithm has been improved. Automatic log file rotation for virtual hosts configured through Apache httpd.conf has been added. A bug in the AJP Protocol that caused problems with the winstone servlet engine has been fixed. A bug in HTTP Proxy that caused a problem when the upstream Web server did not set the 'Content-Length' header has been fixed. A bug in request parsing that had problems with special values in the 'Connection' header has been fixed.

RSS Recent comments

30 Jan 2010 08:51 PierreG

@ Woods:

> "I also really dislike the idea of binary-only BLOBs being labeled as "freeware" on Freshmeat"

Actually "freeware" is not necessary open-source. To avoid any conffusion, the Free Software Foundation asks open-source authors to avoid calling their software "freeware":

en.wikipedia.org/wiki/...

And Freshmeat welcomes "freeware" as well as "open-source" as both arguably provide value to users.

27 Sep 2007 11:07 phr3ak

chroot
chroot is really working?

02 May 2007 22:00 Avatar woods

Re: License of "Freeware" isn't very free

I also really dislike the idea of binary-only BLOBs being labeled as "freeware" on Freshmeat. It definitely goes against the spirit of anything I would expect to find labeled as "freeware". I expect freeware to have source available.

> Our goal is to provide an easy to use,
> secure and high performance web server
> product with the best value for all
> level of users instead of a so so open
> source project. Close source is easier
> for us to maintain the quality,
> performance and security.

That sounds like a pile of VERY poor excuses.

Closed source software is NOT actually easier to maintain, and in fact it's likely going to be of much lower quality and performance, and have less security too, than if you published your source code.

You simply cannot hope to attain the highest levels of quality, performance, and security without having far more eyes than just your own looking at your code.

Note that just because your code is open sourced doesn't mean you have to accept changes back or even allow for redistribution, and you can definitely restrict redistribution of modified copies (though that's beginning to go against the spirit of open source). I.e. you don't have to follow common open source development practices just because you publish your source code for everyone to examine, fix, change, and build for themselves.

I for one would never ever have looked at your product in the first place if I had known the source was unavailable.

07 Mar 2006 01:16 Jshand4

Dmg
where's the .Dmg for Mac OSX?

16 May 2005 14:41 johnnymason

Great Job
Excellent results so far. Looking forward to future improvements!

Screenshot

Project Spotlight

libHX

A library for quick day-to-day C programming.

Screenshot

Project Spotlight

Wandora

A Topic Map editor application.