Search results

That's because no index file is available, and autoindex is off, before, it returns 404 not found, but another user said, Apache return 403, so we change it to match Apache behavior.

Are there rewrite rules in .htaccess of the root folder? Random error is hard to debug, and we need at least some debug log for request results in 404, with rewrite log enabled, in order to look it further. It might have something to do with htaccess cache updating. Is that possible to...

Do you have any request filter rule configured? Maybe turning on "Debug logging" by set "Debug Level" to "High" will help.

Looks great! Thanks! :)

Yes, just run the install.sh, then select "upgrade", your current configuration will not be touched.

Yes, you can give it try. It might work if the permission of production log and log directory has been set properly.

It requires "socket" module, you can check the configuration line with "./admin_php -i".

Maybe the prebuilt PHP does work well on your server? You can try to replace lsws/admin/fcgi-bin/admin_php with a PHP binary built from source. Or, it is related to the new PHP 4.4.7 release. We have not heard this problem from other users yet.

Yeah, that's the right way to let all PHP process share the same opcode cache.

Lazy. ;) The bug was fixed shortly after the initial release, so I guess not many users have downloaded it. Unfortunately, forgot to update the tgz package. My bad.

It turns out that we only updated the gem package, but not the tgz package on our web site. Just updated it, please download and reinstall.

That's true that LSWS does not check the q value. Is it possible to remove "gzip" completely from the header? It will save some effort on both side. ;)

I think you probably is not actually using the latest ruby lsapi 2.5. Manual installation will have higher priority than GEM installation, make sure to remove all lsapi.so under your ruby library directory and reinstall again. "?image" is caused by a bug in earlier 2.5 release package, should...

We are in the process of updating the web site.

Those articles looks great, I will creat links in our wiki.

Checkout one tutorial posted by a litespeed user http://creativeflux.co.uk/entry/replacing-apache-with-litespeed/ We probably will provide a script to build lsphp more easily in the future. LiteSpeed PHP installation is completely independant to cPanel's php installation, if you do not mix it...

That's great! Thanks! :D

Thanks! It will be a better reward if you can help us spreading the words in the django community. :D Also, if you do not mind, please help us updating the dyango wiki entry http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:django_fcgi_python Have fun! :)

UDS socket is created by the server. Is the python process running, maybe it dies immediately. One way to trace it down is to use "strace" to trace the djyango process, command is like strace -o strace.log <orignal FCGI command> You probably cannot use this command directly in the App...