Search results

Use this option in your LSWS http://www.litespeedtech.com/docs/webserver/config/general/#useIpInProxyHeader

Checked the tcpdump output, the client sent a HTTP GET request with request body, which does not follow HTTP specs. Should use "POST" request method.

That's possible. move to 4.0 release section.

Banned IP will be listed at the minimum. We won't do traffic log analyzer in side the server core. use those external packages.

Signal 9 is SIGKILL, it won't be trigger by anything other than sending by anther process to kill the process off.

1. the request URL should has been logged in error.log, but not in audit log. 2. No, we won't do that, leave it for developer using rewrite rule or something. 3. Our web console have option to compile PHP now. 4. Yes, I want that too. 5. No, just show the last few lines by default. 6. Maybe, may...

What is your timeout value with the update release?

do the following: lsws/bin/lshttpd -m lsws/bin/lshttpd -r mv lsws/license.key conf

Forget about Zeus, that web server is dying. they have abandoned the web server product.

We are internally testing the cache function of the 4.0b1 release. From time to time, we will switch between 3.3.9 and 4.0b1 releases. If you experience any problem with our site, please report to this thread.

Do you get this error frequently? The keep-alive timeout definitely play a role here. 35 seconds should help. I have change the timeout calculation in 3.3.10, you can give it a try by changing the version number in the download link.

OK, fixed in 3.3.10 build. You can download and give it try by changing the version number in the download link.

Yeah, we can do that.

I don't think the process priority can affect the performance much, as long as the server load is not high and PHP is not in a dead loop, the CPU spikes are normal due to the fact that LiteSpeed only use a handful persistent PHP process to handle all PHP requests.

Showing bytes completed is a good looking but useless feature to me. Instead, number of connections from each IP established now and in the past minute, blocked IP that attacking your server, IP that consume most of your bandwidth etc are more useful information than those micro details.

cPanel was killing lshttpd with "-9", the wrapper script should fix it.

Looks like your handheld sends a request containing invalid characters or some thing. Please use tcpdump to dump the request packet and send the output to bug@ ... , we will check if we can address it.

Probably after our performance tuning is done to the 4.0 release.

"epoll" is the "best" on 2.6 kernel.

Improving status page is on our 4.0 to-do list. I might be wrong, but I don't think showing hundreds of connection detail status really help. The detail status will change 100 times/second. It has to be some statistical data that makes sense.