Search results

Put the security rule in your httpd.conf

Not necessary with 3.3.5 release any more, native implementation has been added. DirectoryIndex index.php index.html index.htm default.htm default.html RewriteCond %{REQUEST_URI} ^(.*)/(\?.*)?(\#.*)?$ RewriteCond %{DOCUMENT_ROOT}/$1index.php !-f RewriteCond %{DOCUMENT_ROOT}/$1index.html !-f...

You need to implement it with rewrite rules in .htaccess. Google is your friend. :)

yes, "Connection Keepalive Time" tells LSWS when to close the connection between the web server and external application.

"Max Idle Time" tell LSWS how soon to kill the ruby process. "LSAPI_MAX_IDLE" tell the ruby process how soon to exit by itself.

Just add header( "status: 200" ); to you php code.

It is a internal redirect for "/index.php" in both Apache and LiteSpeed, user's browser won't change to "/index.php".

Maybe another easy solution to replace both rewrite rule and DirectoryIndex is to use

has not been implemented in LSWS. We will add that implementation. Is that a plain redirect, or some special variables added in Apache? How about changing your rewrite rule to I think the rewrite rule is duplicate with "/index.php".

Thanks for the bug report. Yes, the case you described does exist, as it is ambiguous when LSWS map a URI to file system, right now, LSWS give the real directory higher priority. we will think about a solution, but it is low priority as there are work arounds available.

"Max Idle time" tells LSWS when to kill the process/application, while "Connection Keepalive Time" tells LSWS when to close the connection, while the process serving the connection may still running, ready to serve next connection. Those configurations control web server behavior, while...

Please try above environment variables, see if it helps. Also, please check the PID of "ruby" processes, see if the killed process is a child process. On a busy server, there should be a parent ruby process keep running. At least, we can narrow down which process send the SIGTERM signal...

LSWS request filter is our implementation of mod_security, it uses mod_security 1.9 rules. If you use LiteSpeed + cPanel, security rule have to be configured from httpd.conf, the original mod_security rule should work just fine. Just do not expect LSWS to block any request results in 404.

does LSWS serve .rhtml directly? or served by rails internally? if it is the later. it must be rails problem, maybe Rails' cache.

LiteSpeed is on now. I set Apache Port Offset to 0. A restart takes about 3 seconds, including scanning .ls_rails configuration for each user, if you turn off rails support, it will take less than 1 second.

OK, the latest 3.3.5 package should have fixed those issues.

I will upload the new build and give it a try on port 2080, please keep the ssh access available to me before the issue has been solved.

Is it a text file? Maybe it is the gzip cache, you can turn off gzip compression if you can. Or, you can remove the gzip cache directory.

does admin_php run as "www" user? what is the onwer and permission mask of /usr/local/lsws/conf ?

Nothing to worry about this warning.