Search results

We will give it a try in our lab, I think the rule should work. Are you using the standard edition or Enterprise, only Enterprise support mod_security rules.

We cannot help you with this kind of information. It is not enough. You need to show us the Apache configuration that bans your IP. You can PM me if you want.

How do you configure the mod_security rules in httpd.conf? What make you think mod_security rules is not working?

Same as how would you configure mod_security for Apache if you use LSWS with httpd.conf, otherwise, check our document regarding request filter.

do "env | grep PATH" from a terminal window.

The error is pretty obvious already, you should set "PATH envrionment" to include the directory hold gcc binary. just use PATH for your shell. config.log is in the expanded php-5.2.5 directory.

Which control panel are you using, looks like LSWS think a secure site has been configured on that IP:port combination. Can you please send your Apache configuration file httpd.conf and all included configuration filr to bug (at) litespeedtech . c o m

Maybe the PHP process has been stopped due to the long idle, please check the PHP LSAPI page for configuration options to keep it running.

add IP address as the site alias

Yes, that's correct. The same for each rails application behind the scene. If you guys can make it into the official rack package, it will be great.

Just remove the "public" appeared one by one, when you define a rails vhost member from the template, make sure do not append public to the vhost root configuration. it should point to the root directory of your rails application.

Maybe MIME type problem, and the result was cached by the browser. clear the browser cache and try again. Make sure to use the latest LSWS release.

Do not use lsruby_runner.rb, just run simple.rb directly by changing the command configuration, use a LSAPI context instead of *.rb script handler to invoke the app. AEM's code should work. And if you want to make your code works, I think you need a little more changes need to...

have you added "require lsapi" ? other changes need to be made are rack.run_once=false LSAPI uses hash to store ENV, so need to do env=ENV.to_hash, just env=ENV

It is a lot harder to do what you want. and some are just one time job, some require special permission, etc. Every system is different, it closes to be impossible to make it work well on all the platforms. When you need to upgrade your PHP binary, you will appreciate the GUI.

http://www.litespeedtech.com/support/forum/showthread.php?p=8160

That's caused by large request body, LSWS store large request body in swap memory, and the partition hold the swap directory may be full. the default swap directory is /tmp/lshttpd/swap, you can change it to another directory.

Thanks for the update. The extension should have been installed into <your_php_prefix>/lib/php/extensions/no-debug-non-zts-20060613/

LiteSpeed does not have the infrastructure in place to manipulate the response, just send it as is. It is possible to implement something with an external LSAPI filter, but it is not efficient.

maybe the PHP 5 build does not have all required modules to run your PHP script, please check error.log and stderr.log. Do a "strace" on the PHP process if still no clue.