Search results

You can safely assume it is a persistent CGI container, all CGI environment variables is available. On top of that, you can craft a Mongrel HttpHandler object and make Merb think it is running under Mongrel. ;)

SSI is not supported by LiteSpeed yet, .shtml will be served as static html.

I think it is possible, LSAPI is a communication protocol between LSWS and ruby, should be able to run anything on top of that. The hook between LSAPI and any ruby web application should be very simple, just take a look at our RailsRunner.rb. You can try make a hook to the Merb in pure ruby.

The max connection limits is the number of concurrent client connections a server can have, no matter how the requests should be processed. Why not let LiteSpeed handle the dynamic pages directly, it should be much more efficient than forwarding to backend apache. :)

Checked the .htaccess problem in /cgi-bin/ dir, it is because there is another ScriptAlias directive for "/cgi-bin" pointing to /usr/local/apache/cgi-bin/ in the default vhost, and that directory has "AllowOverride None" in it. So, our httpd.conf parser was confused. It should be fixed in the...

You can change your vhost root to "/home/test/", set document root to "/home/test/app/current/", change the "Rails" context location to "/home/test/app/current/" as well. This way, you can set awstats working directory to a real directory at "/home/test/awstats". You need to instantiate the...

What directives are in the .htaccess file under /cgi-bin/ dir? I will take a look.

Testing over localhost has minimum impacts on the results for the Rails tests, as "ab" will only take minimum resource. For the static file tests results, however, the differences should be much bigger if tested remotely, given your network is fast enough. It will only make LSWS looks even...

Thanks for sharing this with us. :) LSWS+mongrel score is not as good as we expected, we will take a look when we get a chance. Anyway, LSWS+LSAPI is the number 1. ;)

Took a brief look at Django document and flup code, I think it should work well with LSWS. Just a little tricky for the FCGI startup command. If you want LSWS to manage the FCGI instances, you can try: MaxConn: 20 (<50 is OK, flup support upto 50 connections by default) Auto Start: true...

Great! Thanks for the update. LiteSpeed should give a big boost in speed since Apache's htacess implementation is extremely slow. Would you mind giving us some number shows how much the improvments is? :) Do you have plesk server? We would like to verify the httpd.conf generated by Plesk as...

You can check our hotlinking control options, or you can implement similar access rule with URL rewrite. More complicate checking can be done with in your script I think.

http://www.litespeedtech.com/support/forum/showthread.php?t=783

My bad, it's a bug introduced while fixing previous one.:p For the second one, install script has been updated to make default.php is copied over despite the error message. Please give the updated package a try.

For the Directory directive problem, please download the updated package again, should be fixed. For the hanging problem, you can "strace <pid>" or attach to the process with GDB, with command "attach <pid>", then "bt", post the backtrace of stack. Or, you can try "kill -BUS <pid>" to let it...

See if we can make it into the 3.0 official release then. :)

We certainly can prioritize this feature if there are enough interests in it. :)