Search results

Sorry about the delay, have make 4.1RC2 package available.

New features are: AIO support upload progress bar support All bug fixes and enhancements from 4.0.11 release. only linux package is available now, We have not make much progress on feature promised for RC2 yet as we focus on address some important issues in our 4.0.x release branch, the good...

No plan to support it.

Can you double check that the user that Apache run as can access the password file? sudo -u nobody cat <path_to_.htpasswd>

You can try pointing to /dev/null

Our dedicate email support is a paid service.

timezone does not matter, as LSWS does not use local time internally, timezone has no effect. It only affects logging.

It is completely up to the task scheduler of the kernel, not likely be controlled by user land application, no matter it is single-threaded or multi-threaded application. Even if you can control that, you should not, as the kernel task scheduler usually does better job on that.

No. content-length must be set.

LSWS resolve the symbolic link when a site is restrained.

Are you using the enterprise edition? For perl you need to check the CGI related limits, memory/process limit etc. Under server security tab.

Please try changing <VirtualHost *> to <VritulHost xx.xx.xx.xx:80> see if it help or not.

Need to check parent directories as well.

There are still response header and body with 403 error page, it still consume bandwidth, it wont use PHP unless the custom error page is written in PHP. You may want to block those IP at firewall level.

chmod g+rx <path>

No, prefork only. LSAPI itself can work with multi-thread, but it is not widely used/tested. Ruby support true multi-thread now? not just software simulated fake multi-thread?

4.1 release with AIO will do much better in this regard.

Thanks for the tip. The problem is that we need to keep the script compatible with all Rails versions. One API function may appear/disappear from version to version. It may work for one version, then stopped for next. Very hard to maintain.

Rails developers keep changing the API, I do not know exactly which function to use. :( ActiveRecord::Base.clear_all_connections! is a delegation to ActiveRecord::Base.connection_handler.clear_all_connections!

If there are enough memory on your server, you can move php opcode cache to under /dev/shm.