Search results

Maybe it need updates on the LSAPI object definition. Make it derive from "File" object could make irb happy. It is in ruby-lsapi/ext/lsapi/lsruby.c inside Init_lsapi() function.

Thanks, suggestions are taken. :)

That's correct. should not be a problem.

you need to patch utility/buildPHPExecute.php before we release an update.

Currently scanning response body is not supported by LiteSpeed yet. A rule like that will severely slow down the server when scan a large response body. So, we will think about it carefully.

it is not possible when LSWS read Apache httpd.conf. Only when you using LSWS vhost template you can do that.

Have taken some time to investigate it tonight, I think a piece of code similar to rails-2.3.0/lib/commands/server.rb should work, the main change is to use our Rack handler instead of Mongrel or WEBrick for the server object server = Rack::Handler::LSWS Might need some tweaks like our...

That's because lsphp and lshttpd communicated with each other using File handle 1 (STDOUT). We just released LiteSpeed PHP SAPI 4.9 to address this issue. If you use cPanel, just Build matching PHP binary again, you probably need to switch back to Apache, and remove...

Seems the query string part has been handled properly in LSWS already, Please give us more detailed description about the problem.

The response buffer will not buffer the whole response, it is just wait a little bit longer to combine fragmented response data into a larger piece. LSWS always read the response as fast as it can and free the backend connection regardless the "Response Buffering" option.

That's because the query string in the target URL, we will make it work in 4.0 release.

You are right about the .reconnect. .clear_active_connections is for backward compatibility with earlier release.

One PHP module write "No recip..." string to STDOUT directly, which causes this error. usually, it is caused by "printf()" in PHP module written in C.

Yes, we will consider it.

Maybe your partition is out of space, please check output of "df".

try to remove the space between "|" and "/htdocs/....".

does it show that /usr/local/lib/php.ini is being used?

"RewriteOptions inherit" will be added.

You have to add "RewriteLogLevel 9" to the vhost configuration to enable rewrite related logging.

After study the behavior of Apache rewrite implementation, it is the correct behavior. If you put only "RewriteEngine On" in a .htaccess without any rewrite rules or "RewriteOptions inherit", Apache will not look for other rewrite rules in parent directories. Tested it on Apache 2.2 . So, we...