Search results

  1. M

    [Fixed] LsAPI integration breaks __DIR__ in CLI

    if you update to latest build of LSWS 5.0.9, it will build PHP with LiteSpeed SAPI 6.9 .
  2. M

    [Fixed] LsAPI integration breaks __DIR__ in CLI

    It has been fixed in PHP LiteSpeed SAPI 6.9 release.
  3. M

    [Fixed] Server breaks HTTP/308 redirect responses and does internal silent rev-proxy

    Please update to latest build of 5.0.9 /usr/local/lsws/admin/misc/lsup.sh -f -v 5.0.9 should be fixed.
  4. M

    LSphp55 ?

    Yes, it is intended for PHP 5.5, for PHP 5.6, it is better to add lsphp56. Make configurations consistent with PHP version.
  5. M

    LSphp55 ?

    yes, you can remove it if you do not need to support PHP 5.5.
  6. M

    [Fixed] Server breaks HTTP/308 redirect responses and does internal silent rev-proxy

    Yes, 308 response should be pass through to clients instead of doing an internal redirect. We will have it fixed soon.
  7. M

    OS X release

    It requires updating the build tool chain to build 5.0 packages, and OS X is not popular for web server applications. We decide to discount OS X packages for 5.0 unless there are significant demand from our paid customers. If you want to use LiteSpeed on OSX, please try our OpenLiteSpeed product.
  8. M

    Upgrade No Longer Works

    rm -rf /usr/local/lsws/autoupdate/platform then try again.
  9. M

    [Resolved] Out of memory errors in Admin interface

    The memory limit for admin_php is hard coded. please try the updated 5.0.9 package with /usr/local/lsws/admin/misc/lsup.sh -d -f -v 5.0.9
  10. M

    [Resolved] 500 server error when switch back to Apache

    You need to check Apache error_log to find out the root cause.
  11. M

    Truncated command line

    Yes, there is size limit, if do not truncate, the lsphp process may crash. To make it longer involves code change in LSAPI implementation and other components.
  12. M

    Litespeed Virtual host with Cpanel and apache(APVH)

    You can use Apache directives for Access control. Per client throttling can only be set at server level. You can set per vhost bandwidth limit through mod_bw directives. "BandWidth", "MinBandWidth", "LargeFileLimit" directives are supported.
  13. M

    Problems With Mod_Rewrite

    You may want to turn off APC opcode cache temporarily, see if it helps or not.
  14. M

    Problems With Mod_Rewrite

    It could be missing required module in PHP, you need to contact your hosting provider about this, it is a PHP setup issue, not rewrite issue.
  15. M

    Problems With Mod_Rewrite

    For PageKit, we need to check the site to find out what prevent it from passing installation stage. The rewrite rule looks pretty normal. We may need to check the your site to find out what happened.
  16. M

    [Fixed] LsAPI integration breaks __DIR__ in CLI

    You need to fill bug report to php.net regarding PHP CLI, our LiteSpeed SAPI is not for lsphp, wont affect PHP cli binary.
  17. M

    Litespeed Virtual host with Cpanel and apache(APVH)

    for cache https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscache:setup-guidline and there are specific guides for different applications. not sure about what you want for security.
  18. M

    WordPress cache plugin

    yes, all are on our to-do list.
  19. M

    Letsencrypt is coming

    It is just a script to crab a cert from remote server and update server configuration. If it can update Apache configuration file automatically, it should work with LiteSpeed when LiteSpeed is configured to load httpd.conf.
Top