Search results

I think you need to update cagefs to include ruby lsapi. it only installed at server level, but not included in cagefs for each user account.

Session handling is completely PHP internal feature, not directly related to any SAPI. It is likely a problem with you PHP configuration.

Please try 4.1.13, /usr/local/lsws/admin/misc/lsup.sh -v 4.1.13

Please download and manually upgrade to latest 4.1.13 build.

lsapi application run in its own process, just like FCGI, what you want is not possible with LSAPI app.

Please upgrade to latest 4.1.13 build, Apache behavior has been followed now. from command line do: /usr/local/lsws/admin/misc/lsup.sh 4.1.13

Please upgrade to latest 4.1.13 build, it should be addressed. you can do it from command line /usr/local/lsws/admin/misc/lsup.sh 4.1.13

It is caused by missing file in CageFS skeleton, did the following fix it. edit /etc/cagefs/conf.d/perl.cfg by adding to paths then run command then everything works as expected.

those vulnerabilities does not affect LiteSpeed PHP at all even you are using the older releases.

Please PM me a temp root login to your server, will take a look.

use email address from your ISP, or your business. Free email is not allowed.

as long as you do not get 503 error in the log, there is nothing to worry about the "Connection reset" message. litespeed can recover when it happens.

Yes, it is on our to-do list of our lsphp suEXEC daemon development, will be in our 4.2 release.

Please be more specific with your test case that LiteSpeed does not support basic security rules, so, we can look into it. The rule you think should work. The test request/URI, related File/script. In order to reduce the cost of heavy mod_security rule, LiteSpeed takes shortcuts in many...

uploaded a new build of 4.1.12, the bug should have been fixed now.

Would you like to help us figuring out what is wrong with this? If yes, please remove existing error log, change "Log Level" to "debug", "Debug Level" to "high", do the test again with 4.1.12. send us the log file, along with you IP address, so we can track related log entries in error.log with...

%20 wont work, You need to escape the percentage character "\%20".

Please try "Force reinstall" of 4.1.11 from web console. RewriteRule ^documents/VCOSS_docs/(.*) /documents/VCOSS\%20docs/$1 should work now, same as with Apache.

Please turn on rewrite logging with RewriteLogLevel 9 You need to put that directive in the vhost configuration section for that virtual host. Then check error.log for related log entries. You can either post it here, PM or send to bug@litespeed... And, we need more information about your...