Search results

You can use a piped logger to filter the log entries of image files. If we add a feature like that, it would be Enterprise only.

Maybe the listener to vhost mapping to the second vhost is wrong, so it served by the first vhost. turn on deubg logging, and check error.log.

Whether sendfile can be taken advantage of is determined by the kernel. It should not hurt even it is not supported by the kernel. mod_security configuration for the apache vhost is independant. The requet filter configuration in admin console has not effect to apache vhosts.

The Rails easy configuation is a lot easier. A lot of configurations has been automated behind the scene. The end result is the same for a simple rails app setup. The manual configuration give you more flexibilities if you need it.

This should be allowed in the admin console. if you manually edit the config file, it should work.

The easiest solution is using our Rails vhost template, it is based on our easy configuration. Our Wiki should be editable by any forum user. Feel free to and your doc there.

OK, got it. The fix should be in the latest 3.2 build.

http://store.litespeedtech.com/, the main web site will be pdated soon.

It does not matter if you use "PHP suEXEC", "PHP suEXEC MaxConn" is the limit for each user. I don't recommend setting connection and childrens too high.

I don't think it is the rewrite rule. You can add "RewriteLogLevle 9" to the configuration of this vhost in httpd.conf. then check the rewrite log in error.log.

Are you using 404 handler or the rewrite rule to dispatch the requests? Is there an admin directory?

That's smart solution. :)

I thought our lsws/admin/misc/rc-inst.sh should do that for you.

set "Auto Start" to "on", make sure you can execute $VH_ROOT/public/dispatch.lsapi from command line.

Please turn on debug logging, and check your error.log and stderr.log. Unless you changed the external app configuration, the executable should be named as /opt/lsws/fcgi-bin/lsphp, instead of "php", php.ini should be at /opt/lsws/php/php.ini.

You can implement this with rewrite rules, like what you would do with Apache, it is more flexible.

looks like you need to rebuild your openssl library, different version of libcom_err.so were referenced by different libraries.

No. It does not. You should not let root own the document root. Only the CGI that need to executed as root should be owned by root with SetUID bit set. LSWS will not start any CGI process as root, period. However, a SetUID process will change the user id to who own the file by itself.

You should not mix the easy configuration and manual configuration together. Just pick one you like. Both works.

LiteSpeed will not start any CGI with UID less than 10, but a Set UID CGI will change it UID to the UID of the owner of the file after it starts. make sure to let LiteSpeed allowing Set UID CGI.