Search results

OK, I will check.

You need to try a bit harder to stop browser caching pages. consider the following headers. ;) Pragma:no-cache Cache-Control: no-store, no-cache, private, max-stale=0 Expires: 0 Good luck! :)

Step by step wiki for compiling your own PHP binary is available http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi You don't need to replace the old php binary, just name the php binary as "lsphp5" instead of "lsphp". Once you get the lsphp5 binary, just duplicate...

3.1 will be released soon, maybe next week. "servlet engine" should be a bit faster than "Proxy", but is also depends on winstone implemenation. one big difference is that winstone cloase HTTP connection for each request, but keep the AJP connection persistent. So, "servlet engine" should be a...

I noticed that as well, after some investigations, I found that Winstone always dumps this error whenever the the AJP connection was closed by LSWS, like when LSWS restarts. I think it is normal and does not really affect anything.

Cool! The little servlet engine hits two bugs in LSWS. ;) Just uploaded 3.1 release with fixes, please download and try http://www.litespeedtech.com/packages/3.0/lsws-3.1-std-i386-linux.tar.gz

You need to compile your own PHP5 LSAPI binary, then duplicate the existing configuration for PHP4, just make sure the script handler is for ".php5" suffix.

There is no problem with the rewrite rules. Two possibilities, one is that browser cache the page, you can verify it with LiveHeader extension, if browser uses a cached page, there should not be any new request sent. You can verify that at server end with access log as well. Another...

Ruby LSAPI 2.4 and PHP LSAPI 3.1 released: Download: http://www.litespeedtech.com/products/webserver/lsapi/ Overview: Ruby LSAPI is a Ruby extension which implements the highly optimized LiteSpeed SAPI protocol between Ruby and LiteSpeed Server. PHP LSAPI is a PHP SAPI which...

I probably misunderstood your problem. I think you need to add "no-cache" header in the dynamic response to prevent the browser from caching pages.

LSWS does not cache cookie values, it just use what received in the request. You can check the cookie value with firefox LiveHeader extension. Make sure to clear the cookie value when a user logout.

OK, we reproduced the problem. Please download and try ruby-lsapi 2.4 package: http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-2.4.tar.gz An new environment variable LSAPI_EXTRA_CHILDREN has been added, please check the README file.

Are you using 2CPU enterprise? The server should not increase the max connection on its own. Which version of LSWS are you using? Maybe should upgrade to the latest one if not yet. Is it possible for me to login your server and take a look? If yes, please PM me a temp login. That's normal...

We are little behind schedule. LoadBalancer 1.0 will be announced sometime in next week. And the cache will be available about a month later.

There is no need to to change if you use it in a .htaccess, if use those under a vhost rewrite tab, you need to add "^/*" prefix like some of the rules in your post.

LiteSpeed follow the standard CGI route, so STDOUT goes in response. So, it is not possible to make LiteSpeed act as mongrel at this moment, we will try something. For logging purpose, please use "STDERR".

The parent process will added one extra process. <<1 is left shift, which double the value.

We updated YUI to the latest release, please give it try see if it helps or not.

LiteSpeed Web Server 3.0.3 has been released. Download LSWS: http://www.litespeedtech.com/product...rver/download/ Changelog for LiteSpeed Web Server 3.0.3: Improved Apache mod_rewrite compatibilities. Updated YUI code to 2.2.1 in web administration console. Fixed a bug that causes...

This is caused by a bug when the reply is very big, we had fixed this problem in 3.0.3, please give it a try. However, the maximum reply header size limit might be hit. The limit in LSWS is 8K.