Search results

You have to remove the passcode of the private key.

You can make /etc/ssl/private/ world readable temporarily, after save the configuration, then lock down the permission. This issue will be addressed in next release 4.1.3 .

AIO has no effect on dynamic site.

It will crash PHP, you can give it a try, the source code can be modified as your wish.

must be triggered by request header "Accept-Encoding: gzip, deflate" .

You can use "-1", keep alive as long as the PHP process is alive. It is the default I think.

Please force reinstall 4.1.2, more bug fixed for this issue.

Just let LSWS read httpd.conf http://www.litespeedtech.com/docs/webserver/config/general/#loadApacheConf

what you mean PHP keep-alive? client keep-alive with server after serving a PHP page? or keep PHP process running after serving requests?

http://www.litespeedtech.com/how-tos.html#qa_dos install CSF, block those IP at firewall.

maybe related to http://www.litespeedtech.com/support/forum/showthread.php?t=5158 try a force reinstall of 4.1.2

Maybe it is the inode limit for /tmp or /dev/shm, not disk space.

Please contact bug@litespeedtech

Sorry, I was wrong, not sure where I got the false impression. We will add the script permission check in our to-do list.

Litespeed does not implement suphp like permission check, if you want, you can use suhosin.

You will see bigger difference if your server is under heavy load. Network latency is playing a role here as well. PHP script itself will run at the same speed inside PHP engine, LiteSpeed's advantage is resource management, PHP startup, passing request/response, etc. The faster your scripts...

I think it is your "umask" setting for root user changed from 0022 to 0027 We will update our script to set the permission right.

if it happen again, please compress and send output of lsof.

It means that web server skips caching a gzipped empty page. It is harmless.

If you are using 4.1.2, please do a force reinstall to update to latest build.