Search results

Maybe it is a configuration problem. Have you configure LiteSpeed to create a listener as *:80 form web admin console? You should remove that listener if you do.

OK. Fixed.

Please follow our wikis, I think there are enough resource available on this topic.

Yes, you can do that.

No, only IP is used to distinguish clients. Usually it is not a problem.

We usually wait a couple days before trigger the autoupdate, just in case any thing wrong with the release. You can update it manually by running install.sh from command line.

OK, we figured out the problem, ForceType uses the global PHP process instead of suEXEC PHP under your own ID. so it has permission issue to access the session file. Will fix this.

Your understanding is correct. LSAPI may start extra children process when more requests need to be processed, please take a look at LSAPI_EXTRA_CHILDREN. To prevent a client exhousting all backend php processes, please try our request rate throttling.

Not sure what you want exactly. If you want to limit access to a Rails application, you can set that in the context configuration.

If possible, please pm me temp root login, I can take a quick look. it is the fastest way to have this issue solved. otherwise, please send your full httpd.conf to bug @ ...

configuration <Files abilene> ForceType application/x-httpd-php </Files>let web server server "abilene" as PHP script, as you noticed that, it does serve as PHP. PHP session is managed by php engine internal, I doubt it was affected by the web server. But anyway, seems the PHP engine like...

You can specify a "-c <php.ini path>" parameter from the command line of lsphp external application.

That probably means that the application does not send back any response header. you should start with a simple hello world LSAPI application, or hello world CGI with the ruby runner. Once you get an idea about the configuration, you can try the complicate stuff.

In 3.2 release, access can be turned off with a simple rewrite rule in enterprise edition: RewriteRule \.(gif|jpeg|png)$ - [E=dontlog:1]

If you creat your own dispatch.lsapi external application, you need to set it in each ext app config.

You should not modify your application.rb to use LSAPI directly if you use the ruby runner. ruby runner is the LSAPI application, which can only run plain CGI written in ruby. If you convert your application.rb to LSAPI, then get rid of the ruby runner. And define a LSAPI context and use it as...

The gem install only works with Rails I guess, unless you explicitly include gem packages. You need to install ruby-lsapi manually.

You configuration is wrong. Plase use our lsphp external app as a reference. /path/to/ruby-lsapi-2.5/scripts/lsruby_runner.rb should be the command to be exeuted, not the socket path. Please check error.log and stderr.log for error messages related.

please checkout scripts/lsruby_runner.rb, creat a LSAPI external app, add a "script handler" to let it handle ".rb" files. All the ".rb" file will be run inside the persistent Ruby Runner process as CGI script.