Search results

Premature end of response header probably is caused by crashed ruby process, which did not send back the response header or just half of it. For 404 -> 503 problem, I don't know why it happens, maybe something wrong with that the way a routing error was handled in your application. Create a test...

Yes, they are. You probably did not enable PHP support during the installation.

Will be fixed in 3.0RC1 release.

run install.sh, you will know.

try to access any PHP script, see if it works. If not, reinstall you server with php support enabled during installation. check you PHP script again. Replace lsws/fcgi-bin/lsphp with your own PHP binary, restart server, check PHP script again. If everything works, try your POST test, if not...

I think your PHP configuration is not right, *.php is treated as static file, so POST is not allowed, check your lsphp external app and script handler configuration, pay attention to the error/warning message when LSWS starts.

You still need to have LiteSpeed reverse proxy to Apache with mod_svn.

Please check our document. No.

You should ask the first question to directadmin team, we have no answer here. For the second question, we need a sample httpd.conf generated by directadmin for testing. If you want, you can send your httpd.conf to info @ litespeedtech ... , we keep it confidiental.

You can view previous months data by swithing to dynamic mode.

You have to logout first, then reply a post without logging in, it will take you to the dedicated login page. ;)

Please try clear the cookie then login again via the dedicate login page, check "Remember me".

It is pretty strange to me as well. Is there any symbolic link along the path? Anyway, it is not a good idea to host website over NFS, it is pretty slow as I/O opteration over NFS will block the server process. Better to host website on local harddisk and sync with master copy of web site on...

Cool! I will add that to our Wiki. Thanks!

fantasydreaming, Thank you for sharing your finding with us. It is really helpful. We may improve the ruby-lsapi implementation to somehow kill those hanging processes when we got a chance. :)

Please give 2.2.6 a try, might be a bug in 3.0beta.

Probably is a bug in 3.0beta admin interface. we'll check.

What is the value of "Use Server Index Files"? should set to "No" if you have index file configuration for that vhost.

Currently, webDAV is not supported by LiteSpeed itself, you need to have LiteSpeed proxy to a webDAV capable backend, like Apache or other server.

It is on our to-do list, at the time we checked mono, it is not ready for prime time yet.