Search results

The ABI for 32bit application built on solaris 8 has been broken on this open solaris release as well as the latest B63. Maybe you should stick with Sun's offical releases or switch to our 64bit binary.

You should use "epoll" instead of "poll" and turn on "sendfile" if you server also serve static files. Consider to install wp-cache to avoid generating the page again and agin. What is the "max connection" for lsphp? do not set it too large to have your server start to use swap.

Thanks! Fixed.

There is no error messages dumped to stderr.log by the PHP engine. When PHP crashes, it is not likely to dump any error to stderr.log. You can remove those core file, then try to access the problem URL, see if there are new core files get created. If yes, try "gdb <path_to_lsphp> <core_file>"...

Maybe a required module is missing in the PHP binary? Please check the directory where the php scripts are, see if there is any core file. errno=2 means "No such file or directory"

Answer to both of your question is yes. The real IP should be the first IP in the x-forwarded-for header, as long as all proxies keep the real IP that way in the header, LSWS will use the real IP.

Please download 2.5 release again, just fixed a bug which have the "?" included in the first parameter of the query string.

My bad, 2.5 package has been updated to have it addressed.

The real IP will be used everywhere once this feature is enabled.

ruby-lsapi 2.5 has been released, please give it a try. The manual installation may mess up with gem install. you may have to remove the lsapi.so created by "ruby setup.rb install".

Make sure php files is configured to be processed as PHP script with script handler either at vhost level or server level.

You don't have to creat a new vhost for the blog, just create a static context to the rails vhost with URI "/blog/", pointing to the location of your wordpress directory. It should work.

It may need some tweeks to make it work perfectly. If you are interested, we can work together on this.

For some reason the QUERY_STRING part has been cut off from "REQUEST_URI" in our lsruby.c. What is the relation between "request_uri" and "ENV['REQUEST_URI']"? Same value? If yes, you can just comment out line 105 & 106 in lsruby.c valLen = p - pValue; *p++ = 0;

Please try the updated 3.1.2 release package, 403 should be returned now.

Thanks for those bug reports. The bug only exists in the Standard edition, we tested Enterprise edition in our lab. :)

updated 3.1.2 release should have this issue addressed.

LSWS does not treat HTTP/1.0 or 1.1 differently on this matter. Have you changed any configuration? What testing tool are you using? You should redirect the result to a file, as the last line of LiteSpeed output is too short, just "missing", without "\n", so it was overwritten by the command...

Yeah, we aware of it. The link in the page is not visible in most browsers. So, we just leave it as is for now. Thanks.

I built a 3.1.2 package for you with the fix to your rewrite rule. Just change the release number to 3.1.2 in the download link to get it. Thank you for raising this issue, our target is to make our rewrite engine 100% compatible with Apache's, no matter is better or worse. It is better to put...