Search results

You need to customize the rewrite rule under the rails context.

Are you using a control panel? If yes, just do what you usually do when Apache is used.

very easy. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:da

I think it is the same problem as this http://www.litespeedtech.com/support/forum/showthread.php?p=12488#post12488

LiteSpeed does not allow serve any static content from a CGI directory for security reason. If you really need to do this, you can use "Alias" or "AliasMatch" directive to tell LSWS that those files should be served as static content.

login to LSWS web console, under "server"->"tuning" tab.

Are you sure the extra CPU time is consumed by lshttpd? Maybe it is the PHP or its opcode cache, does not related to lshttpd itself.

The problem is with your xcache configuration in /usr/local/lib/php.ini. You have to disable it from php.ini, build matching PHP binary, maybe rebuilt xcache.

Please PM me a temp root login for your server.

You may need to reinstall LSWS.

As long as Apache and LiteSpeed setup in the similar way in regard of PHP suEXEC, it is fine to share the opcode cache. If LiteSpeed has PHP suEXEC while Apache does not, it may cause trouble.

Use a rewrite rule in .htaccess to disable it RewriteRule . - [E=no-gzip:1] Above rule will disable it globally. however, you can customize the rewrite to disable gzip selectively.

Yes, it should work. cPanel should not try to establish 60 connections at once though.

Yeah, that's true. suEXEC need root. suEXEC is the best solution, maybe let dreamhost admin install web server as root, give you a sudo permission to start the web server as root.

Set "Port Offset" to allow running LSWS parallel to Apache, apache on port 80, LSWS on port 2080, so you can test LSWS yourself on port 2080, after everything works well, set "Port offset" to 0, and switch LSWS to production on port 80...

It is not safe, as some one may be able to initiate an attack from localhost.

Just uninstall LSWS from WHM plugin and start over again. There is an option to control PHP suEXEC when you reinstall LSWS form WHM plugin. build matching PHP. Make sure to set the "Port Offset", to something like "2000", and open port 2080 from your CSF firewall to test LSWS before put it in...

If the rules are "SecRule", then those are 2.x rules, please wait for 4.0b3, if those are "SecFilter", "SecfilterSelective", those are 1.9 rules, you can use it with current LSWS.

we will try to include the large file support in 4.0b3 release. It has to be either enabled or disabled at compile time, not possible to have both being controlled at runtime. Anyway, the performance difference should be negligible in real world usage.

Must be something wrong the PHP binary created, you can try restart over. Put LiteSpeed on another port to make sure everything work properly, then let it take live traffic.