Search results

  1. M

    Litespeed and TCP Fast Open

    It is enabled automatically.
  2. M

    Cloudflare Proxy IPs(IPv6) - Allowed List

    You can try something like, for example [2400:cb00::]/32T
  3. M

    Newbie to LiteSpeed needs help with PERL access to %ENV variables

    This should be addressed in the latest 6.1RC1 debug build. /usr/local/lsws/admin/misc/lsup.sh -d -f -v 6.1RC1
  4. M

    Proxy context

    Please try the latest 6.1RC1 debug build, the "ProxyPass" should work now. /usr/local/lsws/admin/misc/lsup.sh -d -f -v 6.1RC1
  5. M

    Apache config mode + vhost-level External App handlers

    I see. You can look into bubblewrap more.
  6. M

    X-LiteSpeed-Location - Can only access public_html

    You can create a hidden context (alias) for directory holding those files. Can use rewrite rule to test against %{REQUEST_URI} to make sure it is not a direct hit.
  7. M

    Proxy context

    We will try to support "AllowEncodedSlashes NoDecode", it will take some time, as it is a bigger change.
  8. M

    Apache config mode + vhost-level External App handlers

    Just use detached ProcessGroup with very long "Idle timeout" should be very close to your desired setup. It saves a lot of headache for you to manage those manually.
  9. M

    Proxy context

    Hi, You could use Apache style configuration for
  10. M

    [SOLVED]: Apache "<If>", "<ElseIf>", "<Else>" not supported?

    That's as designed. LiteSpeed tries to avoid the inefficiency of Apache's .htaccess implementation. It is intentional to stop .htaccess inheritance beyond user's home directory. For purpose to apply common config, add it to Apache main config with <Directory /var/www/vhosts/> ... </Directory>...
  11. M

    Server crashing with signal 11 (core dumped)

    Please update OLS to the latest 1.7.16 release.
  12. M

    [SOLVED]: Apache "<If>", "<ElseIf>", "<Else>" not supported?

    "<if> ... <else> ..." should be supported, maybe not perfect, most common directives are supported. Please make sure you are using the latest version. Please post your test cases if need.
  13. M

    Litespeed and TCP Fast Open

    It is enabled automatically, no extra configuration needed.
  14. M

    Litespeed is passing wrong header name

    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto
  15. M

    Apache handled content

    Correct. Update to LSWS 6.0.x, then try to get rid of Apache. LSWS should handle .shtml pretty well.
  16. M

    Issues with a lot of websites on server regularly timing out

    Please follow https://openlitespeed.org/kb/submit-openlitespeed-bug-report/ to get debug log when it happens. Please make sure you are using the latest release of OLS.
  17. M

    Gzip not working and cant update to 6.0.9 version

    Please create a ticket with us, we need to check what happened.
  18. M

    Proxying domain content to a second domain on the same host

    LiteSpeed cannot change the html content of response. it wont work.
Top