Search results

Hi, We have cut the final release of LSWS and LSLB for the year of 2007. Happy Holidays! Every One! LiteSpeed Team LiteSpeed Web Server 3.3.3 has been released Download LiteSpeed Web Server View Version History LiteSpeed Load Balancer 1.1 has been released Download...

You can create a dedicate realm for awstats under vhost->security .

LSWS cannot turn off gzip with environment variables, if the MIME type is XML, you can turn off gzip for that MIME type by removing it from the compressible MIME type configuration.

You need to check what causes the core files using GDB. gdb <path_to_lsphp> corefile bt You can try disable core dump from admin console.

Yes, you can create a Rails virtual host to handle all *.domain, just use "*.domain" as the mapping between the listener and that vhost.

That should do it.

Please refer to the listener to virtual host mapping section of our documentation.

for the staging setup, you need to follow this http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ruby_rails

You can turn off gzip for dynamic content, or use a MIME type that is not in the compressible list.

I think the flash player under IE6, or IE6 itself does not like the response produced by LSWS, while response from Apache is fine. If we can compare the difference between the responses sent by LSWS and Apache, we might be able to find the answer. One quick thought, maybe you can try disabling...

just select update when you run the installer. very easy.

I think you need to use TCP sniffing tool like "tcpdump" to capture the request & response for the refresh HTTP request. If the request appear in Rails log, the request has been delivered to Rails. Please download 3.3.3 release by changing the version number in the download link. A bug related...

The error are different, maybe something missing in the chroot. You can copy over "strace" command to the chroot jail. The do chroot /chroot strace /opt/lsws/fcgi-bin/lsphp -i The output will tell you what is missing. For the xcache issue, you can also check lsws/logs/stderr.log see if any...

chroot /chroot /opt/lsws/fcgi-bin/lsphp -i

You have to use chroot /chroot <php_path> -i to verify everything.

You need to change the static file compression cache location under server->tuning page.

Have been fixed in 3.3.3 release, please download the new release by changing the version number, only linux packages are avaiable at this moment though.

the problem is the chroot, it is not easy to find out what library is missing in chroot. We have to command line tool, lsws/admin/misc/chroot.sh, can help a little bit. chroot.sh /chroot <php_binary> It will fix the missing libraries that linked to <php_binary>, listed with "ldd <php_binary>"...

OK, please try a simple patch to the web console code Open file lsws/admin/html/classes/ws/CLIENT.php, search for $salt = substr($pass,0,2); change it to $salt = substr($pass,0,CRYPT_SALT_LENGTH); Please let me know it works or not.

We will setup a test environment to have this issue fixed.