Search results

Yes, server will send back response in the order they are received. It must be a bug on iOS side. You can turn off pipe-lining by turning off keep-alive. http://www.litespeedtech.com/docs/webserver/config/tuning#maxKeepAliveReq

updateagent binary is no longer required. We will fix the installation script.

Yes, it will be in next release.

It is the first line of the script permission problem.

You can change it via Apache mod_ssl "SSLProtocol" directive.

LiteSpeed does not perform DNS lookup during runtime due to the event-driven architecture, so you need to use a cron job to update the .htaccess with actual IP used. It wont be changed in the near future.

Looks like the status code does not change to 302, try instead. That's right, you need to change your code to set status code to 30x.

You want a "Location" header in the response, but LiteSpeed wont allow it. I got it. You should not use X-LiteSpeed-Location header, only use "Location" header. The most important, you need to set status code to "30x", otherwise, server will treat it as internal redirect. Maybe there is...

What are doing is like input url->/dispatch.lsapi->target url->/dispatch.lsapi litespeed stops it. You may have to use rewrite rule to rewrite the input URL directly to the target URL. then process by Rails. avoid internal redirect in rails that need to be handled by rails again.

The easiest one is to uninstall the "Apache to LSWS wrapper script".

LiteSpeed should be faster than Apache. Any finding? Is it fixed?

Is there really 1240 PHP processes running by that time? If yes, I guess the full backup created a lot of PHP processes running in background. If the server can run more PHP processes, you can increase "LSAPI_EXTRA_CHILDREN", it is 1000 now, it will allow more background PHP processes...

Are you using cPanel? completely uninstall LSWS, and install it through our plugin.

If it is a new server, you need to check if PHP suEXEC is turned on. run /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.21 upload a new file see if the permission is correct or not. The file uploaded with wrong permission need to be fixed manually.

Maybe you can try our lsphp rpms with matching mysql API. we support MySQL 5.1 5.5 5.6 . http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:rpm

you need to change /proc/sys/kernel/core_pattern to /tmp/core-%e.%p PHP suEXEC processes cannot write to /tmp/lshttpd directory.

Which control panel you use? This issue should have been fixed with the latest 4.2.21 build a while ago, please try force reinstall 4.2.21 .

It is controled by http://www.litespeedtech.com/docs/webserver/config/general#phpSuExecMaxConn

The SSL error is at Layer4, no possible to add a layer7 403 error page for that. Neither server, nor client can sen or receive anything from each other.