Search results

You need to change the lsphp5 external app configuration. the command should be set to "$SERVER_ROOT/fcig-bin/lsphp-5.x.x" matching the name of lsphp5 executable.

try changing the gzip working directory under the tuning page, by default /tmp/lshttpd/swap is used, may not have enough space left, or the /tmp partition has been mounted with "noexec".

A HTTP/1.1 browser should support chunk encoding without any problem.

You can trun on response buffering under "Ruby Rails" tab, It won't work reliably for large pages though.

"SSL client authentication" means that you can use a client certification to enhance the security of access to a SSL site.

The compressed gzip version of the file will be stroed in a temp directory, by default, it is in /tmp/lshttpd/swap, you can try change it another directory from the compression configurations. I have seen some issue with /tmp mounted with noexec on 64bit system runing 32bit lshttpd binary.

OK, we will do that.

Yes, you need to go through the access log for the URL.

add "RewriteEngine on" to your .htaccess

OK, changed the log level from INFO to NOTICE for that message

It depends on the timing that LSWS receives the full response from backend application. When Content-Length is not set, "Chunked" "Transfer-Encoding" should use for HTTP 1.1 client. lynx is a HTTP 1.0 client, so none of above header is set. The problem with Safari might not be the header...

Something like RewriteCond %{HTTP_REFERER} !^hl2://xx\.xx\.xx\.xx$ RewriteRule .* - [F]

You can convert it to a rewrite rule.

Please download and try http://www.litespeedtech.com/packages/lsws-3.3.1-ent-i386-linux.tar.gz

Are you using 3.2.4 or 3.3 now?

I did not try the link. Yes, this site is a porn site, please switch to another web server. If you have bought your license recently, please contact sales for a refund.

Request filter "Log Level" is control the debug logging of Request filter, should set it 0 on production server. The logging I refer to is the "Action", usually is "deny,log,status:403". "log" action must be set, and server log level must be set to "INFO", the request URI should be logged with 3.3

Seems works fine in our test environment, please try add "AllowOverride all" in document root configuration section of that user in httpd.conf, if it makes it work, then it might be apache httpd.conf compatibility issue need to be addressed. please send us your httpd.conf for testing.

You do not need to worry about it if there is no "oops" "503" errors in the log. It is normal when a user cancel a request in the middle, but the PHP process is till processing it, then the PHP process was assigned to another request. Eventually, the PHP process will be restarted if won't respond.

What is the problem? Login box won't pop up? or password always fail?