Search results

Please enable the debug logging in LSWS, also check Rails log. Looks like Rails app crashed while handling the HEAD request. You can also try curl with a HEAD request.

looks like a PHP internal problem.

Yes, you can kill them off. They are orphaned processes. Before killing them, please try to exam those processes with strace or gdb "attach". I want to make sure it is not in a infinite loop inside our LSAPI code.

Looks like there is some problem with the built-in install in 3.3.15, please install it manually.

Sorry for the late reply. If you would like, you can PM me or send a temp root login to sales@litespeetech..., we will take a look at it. We can extend your trial if need.

Yes, you can remove them all.

Can you please turn on debug logging by change "DebugLevel" to "HIGH", then try one request and send the error.log to bug@litespeed...

We will add an option to suppress that in 4.0 Enterprise

We will make $VH_ROOT, $VH_DOMAIN, $DOC_ROOT work in next release.

the request filter only inspect the content, does not change it in anyway.

open your httpd.conf, only first five "<virtualhost ...>" sections are imported.

When LSWS was uninstalled via the plugin, the Apache httpd should be restarted automatically, the real issue is why Apache does not get started when "switch to Apache" is selected.

We will look into this issue. Thanks for the bug report.

It is not easy as stderr.log is just a redirection of file handle 2 of external application. We will try to work something out in our 4.0 release.

No, LiteSpeed does not modify the post body, maybe when the third party plugin API is available.

It is my fault, forgot to re-tag the release after applying the patch. Will update 3.3.15 release package with the patch.

access_log will be renamed to access_log.awstats when LSWS update AWSTATS, access_log.awstats is the log file to be processed by awstats. after processing it, it will be archived or removed. If access_log.awstats exists, LSWS will not initiate new awstats update assuming there is one in...

he can do a lot more dangerous things than uninstalling LSWS if he get the root. doesn't he? We need to investigate, what will happen if you click it again? Different user will have different opinion, to me, it will save a lot headaches for some one not very familiar with Linux shell and...

Not, it is not supported. No plan to support it anytime soon. MySQL's license is the main obstacle. However, A fastCGI authorizer can be used to implement that out side of lshttpd process.

It always use the page from its own domain. Should only use relative URL.