Search results

Please create a test application in order for us to reproduce it in our lab easily. We will make it work properly in our next bug fix release.

You can try add "Content-Disposition" header in Rails controller.

OK, here is our test results, Hardware: dual opteron 250 OS: OpenSuse 10.3 x86_64 kernel: 2.6.22.12-0.1-default LSWS 3.3.1 Enterprise with 1-CPU license typical LiteSpeed result typical nginx result: I have done multiple run for each server, those are the typical results. Sometime, the...

application/octet-stream, better use the dedicate MIME type for that type of file though.

You can try the request from command line tool like "lynx -mime_header <url>", or with FireFox module, live-header or firbug. I think the Content-type has not been set properly. Maybe the rails app set "content-type" to "text/html", and the Content-Type has not been overridden properly for the...

It is normal I think, LSWS just abort the Rails request after receiving the redirect in header. Are there more logging entry for 64.135.18.66:55928-0 after the request aborted.

Can please double check if the same php.ini is used? LiteSpeed will use $VH_ROOT/conf/php.ini if available.

The reason of no 403 logged is that the server just close the connection upon accepting the TCP connection, never read the request, thus no way to produce a valid access log entry.

It should be "/URL/to/file", not "/path/to/file". Try "X-LiteSpeed-Location"

Thanks for the information. Can you try nginx with "worker_processes 1;" It will be a much closer match to the 1-CPU license.

Yes the command is like that. You also need to set environment with command like export PHP_LSAPI_CHILDREN=30 Better use a shell script. make sure to change the user id from "root" to a normal user like "nobody" or whatever with "sudo". For address format please take a look at...

When you specify multiple addresses in the list, use a comma to seperate two addresses. It will not give 403 error, the connection will be closed without any reponse. and you will not see anything in access log for IPs being blocked.

Once the lsphp process starts, it will start children processes, the parent process will not die unless it was killed intentionally. Just add it to rc.local or create a dedicate rc script. I think Memcached will not have this issue. XCache probably is the same as APC.

We will setup this in our lab to compare those two. Which version of PHP are you using for the test? What is the configuration for building fastcgi PHP binary for nginx? You run "ab" from the same server? If there is anything else you would like us know about you setup, please let us know.

We will take a look at it tomorrow.

Each lshttpd children process will start its own group of lsphp processes, so it will result in what you observed. With your current 4-CPU license, there are two possible solutions: 1. start lsphp process manually instead of start it automatically by lshttpd. lsphp has a command line option...

That's could be the problem. please try set LSWS_HOME envrionment variable to /home/mydomain.com/lsws/ , see if help.

OK, I recommend the following changes to soellner_php configurations: Max Connections 4 Environment PHP_LSAPI_MAX_REQUESTS =1000 PHP_LSAPI_CHILDREN =4 LSAPI_AVOID_FORK = 1 Run On Start Up Yes Make sure the php.ini used for litespeed and nginux has the same value. You can retry...

If you install LSWS to your home directory, you need to have LSWS run as your user account. looks like it is a directory permission problem. lshttpd cannot locate the installation directory.

Maybe related to this problem. http://www.litespeedtech.com/support/forum/showthread.php?t=1061 Please try "truss ./lshttpd"