Search results

The global per ip src connection limit is the only way to go if you really want protection of high volume bots from your servers. The vhost method doesn't work and will not work in the real-world environment. To protect your VHOSTS in a secondary and more granual protection, use the Per VHOST...

First, the webserver should never let any connection idle beyond the set connection timeout limit. Having no timeout is a much more of a security/ddos risk. Let say you have all your 20 backend lsapi php processes behind litespeed doing heavy calculation for non-specified amount of time with no...

Changing the symlink works but with a gotcha. Sometimes a yum update/upgrade will force the system to rebuild the library links and when that happens, it will revert the symlink back to the original libxml2 library that came with the distro. Overwrite the /usr/lib64/libxml2.so.2.6.26 file...

If on a rpm (redhat/centos) system please install libxml2 and libxml2-devel. yum install libxml2 libxml2-devel Note this is not a litespeed issue.

SecFilterSelective REQUEST_URI "^/proxy" Should work. Note that if /proxy doesn't exists, lsws will not block 404 requests. The above should block anything with yourdomain.com/proxy*

Almost all cases of waitqueue issues have to do with the backend "php/ruby/etc/mysql" not being able to keep up to performance or blocking. For example, if a php script in the backend "blocks" on a tcp connection for whatever reason, mysql, smtp, curl, etc, you can have this problem. This is...

Enabling KA allows much more accurate per client connection throttling. Without it, a client that visit a page with 50 pictures, it's hard to say how many connection his browser might behave and how many connections it might need/user to achieve a smooth page render. So the limits must be set...

It really depends on the website in question, what type of content is pushed, the data distribution pushed back to the client. For example, an litespeed level dos protection strategy for a video hosting site is quite different than one that's only pushing mostly html/text. Personally, I...

Check your php.ini and make sure display errors is enabled. We recommend having it disabled for security reasons.

Are you using LiteSpeed Enterprise or Standard edition? The free standard edition is not designed to handle the the traffic load you are describing.

Yes. The trial server will disable itself after the trial. You can verify this by checking the error.log in the litespeed install location.

You need to get very comfortable with the "apt-get" command in debian os. Look at the man pages for it. You need it a lot. "apt-get install libpng2-dev libjpeg-dev"

To clarify, you need to not only check wether apache_* exists but check the return result if(function_exists('apache_xx') && !apache_xx()) { //use apache_ } else { //use standard method of $_SERVER[HTTP_] }

This is not a bug. The PHP.net documentation clearly states this function is an alias for apache_* function which only works when php is used as an apache module. More over, the roundcube developers, are using seldomly used platform specific php function when they can use and access the...

You need to put the files in the path specified for the particular VHOST (domain). If your VHOST config points to /myweb/dkos.com/ then you put it there.

yum install libjpeg-devel libpng-devel Most likely you will need both jpeg and png libs for php gd to compile properly. Performance tip: if you are going to process lots of large images, don't use GD and use imagemagick instead. Reason: GD will use tons of memory for even simple operations.

LiteSpeed uses a more aggressive and more efficient way of handling dos attacks. When the IP source hits defined throttle ceilings, the request is stopped at earliest possible detection stage.. When an IP hits throttle, LiteSpeed doesn't waste any resources parsing that request's HTTP...

Marcus, Not sure why you have problems with our css style sheets in Firefox. Here is the css response header output form the webui admin: Date Wed, 19 Dec 2007 19:04:26 GMT Server LiteSpeed Accept-Ranges bytes Connection Keep-Alive Keep-Alive timeout=5, max=100 Etag...

The memcached errors has very little if anything to do with litespeed. Really. Here is the way to make sure you have everything set up correctly. 1) Make sure memcached exists on a server that has the firewall disabled. Memcached is meant for a lan setup anyways. 2) Make sure you are using a...

LiteSpeed itself is extremely frugal when it comes to memory so there is not much you need to do. RoR backend would use magnitudes more memory than LiteSpeed itself so you should make sure the RoR setting in LiteSpeed is only spawning a few/low number of instances/children.