Search results

Just released ruby-lsapi-1.11 to fix another bug in ruby LSAPI code, this bug causes incorrect value for " HTTP_X_FORWARDED_HOST" and " HTTP_X_FORWARDED_SERVER". Gem version will take a little while to become availabe, you can download the latest version from our web site. Thanks for your...

Looks like something wrong with passing the request prarameter. Can you please try the following code to dump the request parameters in a .rhtml file? <%ENV.keys.sort.each do |key|%> <%=key%>=><%=ENV[key]%></br> <%end%> And post the result back. I need to get an idea about how bad the...

Can you please try it with LiteSpeed's realm configuration, see if the password file works or not.

Please double check your file path and permission. the user that lshttpd run as should be able to read that file.

It works, maybe the password is encrypted in MD5 format, LSWS works with password created with crypt().

sooner or later. :-) No definitive time table for this yet.

It is because your C compiler is picky, the package has been updated to address this. gem version will be available a few hours later after mirror has been synced, the package on our web site has been updated.

No, it is not possible with LSWS now.

It is controled by "Connection Timeout" http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout You can increase it to 600 seconds.

Yeah, you need to update that. :)

You need to backup lsws/conf directory and restore it after reinstallation.

this problem has been fixed in our code base, will be available in next release, 2.2.3, possibly.

Can your PHP script from command line with CLI version of PHP to make sure it is not a PHP problem?

Maybe it is the fault of FCGI_WEB_SERVER_ADDRS, please try with it being removed.

Please check your default memory limit with "ulimit -a" from command line. LSWS may not able to raise above that limit when PHP is not started in setUIDMode.

You also need to check the memory limit set in php.ini

Yes, that's the current behavior, you need to create directories manually for now.

Maybe the FCGI instances on the backup machine is still pre-occupied by the first machine, TCP connections is still established between FCGI processes and the LSWS on first machine. To solve this issue, you need to set "PHP_FCGI_CHILDREN=40", so there is always php process available for local use.

You should be able to switch back to older release with lsws/admin/misc/mgr_ver.sh 2.2.1, if it does not work, just replace "2.2.2" with "2.2.1" in our download link to get the older package.

Really should remove the "auto restart" option, as there have been many features depends on that. For the "fix 503 error" can not be disabled problem, I will investigate.