Search results

Do you mean "Redirects" function in the "domains" section? Or something else?

Glad you make it work, it is 100 times more efficient. I think it should work with range request.

I think openbase_dir is the problem, just load a phpinfo() page see if openbase_dir is there? You can edit the httpd.conf directly to comment out the openbase_dir configuration for that vhost.

Just create a static context or use "Alias" directive in Apache httpd.conf to make the file accessible. we can put the change in 4.0.4 release. the next build could have the change.

You should create a listener for the dedicate IP that the high traffic site uses, bind multiple processors to that listener. If the site is powered by PHP, make sure you have a php opcode cache installed. If some page can be cached, you can start to think of using the page cache function in...

If what the PHP script do is to stream some media file after authentication, you can use our internal redirect, the target URL is invisible to end-user. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect I think we can up the limit to 2GB in our next...

You need to add a new rule like RewriteRule ^([^.]+\.css)$ /cache/%{HTTP_HOST}/$1

How do you make cPanel create rule like that? The default rule does not look right, as it redirects request with "domain.com" to http://domain.com/, so it causes loop redirections. I don't know why Apache does not cause loop redirection with it. We need to investigate.

Please check the RailsRunner.rb in the latest 4.0.x release, it should be compatible with both v2.2 and v2.3. You may need to explicitly specify the rails version with "RAILS_GEM_VERSION" in environment.rb if you want to use rails 2.3.x

sorry, a typo, should be the "right one". Does "gem list" show "right_aws"? Maybe it was installed as a user level gem, not a system level gem.

You may have multiple ruby install, make sure to use the right now, check it under "Server"->"Rails" tab.

If you use those rule at vhost level, rules look correct. if you use those rule at context level, you need to get rid of the leading "/" as RewriteBase has been removed from URL before matching the Rule. Enable rewrite log and check the error.log if rules does not work as expected. Rails page...

No, not possible to monitor the cache status at this moment. May add it to the real time report in the future release.

php_value inside <FilesMatch> was ignored. You can download and try the latest 4.0.4 build, it should work now.

If you think LSWS does not cache certain page, you need to check the request/response header see if anything prevent the page being cached. Request with Query String? Request Cookie? Response Cookie? Request cache-control? response cache-control? If you think a page can be safely cached even...

Have you built lsphp5 matching that for Apache? phpinfo() from LSWS should show similar output as that from Apache.

You can parse /tmp/lshttpd/.rtreport for now.

How do you do it with Apache? Do the same.

You run /usr/local/apache/bin/httpd as non-root user, you can ignore those messages.

You should try the 4.0.4 build by changing the version number in the download link. With earlier release, you may get 503 error during application startup when Rails app was started on demand and the frame work takes more than 15 seconds to initialize. 4.0.4 should take care of it. You can set...