Search results

We do not recommend using xcache together with PHP suEXEC. If you use PHP suEXEC, just eaccelerator plus /dev/shm. http://www.litespeedtech.com/support/forum/showthread.php?t=2814&page=3

Maybe it is caused by "Restained" configuration, bug has been fixed in 4.0.2 to make it work properly. http://www.litespeedtech.com/docs/webserver/config/vhostlist/#restrained If symbolic links has been used, it could be the problem.

Then you set debug log level to 0, only real attack blocked will be logged.

please try 4.0.2, if it still does not work, switch back and forth between the version that works, see if it is consistent. I think it is something else. I tested the piped logger yesterday in our lab, it works.

I have installed a fresh freebsd 7.1 in our lab. installed /usr/ports/misc/compat6x/ installed 4.0.1, it detects the new release and downloaded 4.0.2 automatically.

We add SuEXEC user/group for external app configured at server level. So, you can have your provider to use your user/group for the FastCGI application added for you. We did not add support for Apache mod_fastcgi directives, so it may break other things.

enable mod_security debug log from httpd.conf and check what happened in the error.log, must be a rule being triggered.

I think you should stop using PHP suEXEC, since PHP run as the user id of the owner of the directory, it can change the permission mask at will, when Apache is used, PHP is running as nobody, so PHP does not have permission to change the permission mask. The solution to your problem is to...

There is no way to prevent the perl script from creating a symbolic link, unless you disable perl. The best can be done is to block access to target file pointed to the symbolic link, above configuration changes does that.

Tried it in our lab, it works.

It should work. Is there any /usr/sbin/cronolog process running? If yes, please strace those processes.

If you use Apache httpd.conf, you should change mod_security configuration there. If you configure filter rules natively, you can try setting log level to 9.

Please read http://www.litespeedtech.com/docs/webserver/config/extapps/ You need to add a FCGI external application, then add a FastCGI context for that application.

Also need to set http://www.litespeedtech.com/docs/webserver/config/security/#checkSymbolLink to "Yes".

Sorry, I still could not understand your English and get an idea what is the problem. Maybe you should post some pictures.

try tuning http://www.litespeedtech.com/docs/webserver/config/security/#followSymbolLink use "If Owner Match"

Litespeed does not like the charset part of the MIME type, You can try you can ignore the other error.

Please PM me the login to the LSWS admin console along with the test URL, I can take a look.

Need more information about your server environment.

No, mod_spelling is not supported.