Search results

Please download and try 4.0.5 build.

It can be easily fend off http://www.litespeedtech.com/how-tos.html#qa_dos

just check the Content-Type return in the response header with firebug.

Our new realtime status page in 4.1 release should address this.

the command parameter points to a PHP4 binary, you should set it something like $SERVER_ROOT/fcgi-bin/lsphp5 , http://www.litespeedtech.com/docs/webserver/config/extapps/#extAppPath

Just check the external app configuration in the suEXEC vhost template.

I think PHP is not in suEXEC mode. double check the PHP command path in the suEXEC template, make sure it uses the right PHP binary.

You can add a matching context to match everything to that page.

There are a few options. first, create a vhost show only the maintanence page. then, you can either update the listener->vhost mapping to show the maintanence vhost. or add a redirect context to direct to the dedicate maintanence page. you need to assign a sub-domain for that vhost.

How the web site being configured? through httpd.conf? or natively via LSWS console?

Found out the MIME type of the stylesheet generated by PHP script. Change "compressible type" configuration accordingly. http://www.litespeedtech.com/docs/webserver/config/tuning/#compressibleTypes

That's normal. memory usage of LSWS depends on number of vhosts configured and the number of concurrent connections. range from 20M-200M.

I think you should remove /home/jms/.gem/ruby/1.8/gems and install all gems at server level.

If you are not running Rails, those messages means that LSWS detects run away PHP processes. the server should fix it automatically, as long as there is no 503 errors, it should be fine.

download and try 4.1rc1

check where is the right_aws gem installed, under /.gem/ruby/1.8 or /usr/lib/ruby/gems/1.8? Should get rid of /.gem/ruby/1.8, it might be for root user only.

Have you restart LSWS? You need to find out which user that the index script run as, it should run as apache user with all the group permission. To find it out, you need patch the autoindex script temporarily, with blow all the function definitions. before The autoindex script should be at...

You should ask your host to help with this, they should be able to enable rewrite log by adding "RewriteLogLevel 9" to your vhost configuration, then check rewrite log in error log file, that's the easiest way to find out the rewrite rule causing problem.

There is a simple solution. http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExec set it to "User's Home Directory Only"

There is no pre-compiled package for LiteSpeed PHP, have built your own after installation. If you can make the package maintainer to add it, that would be great.