Search results

  1. serpent_driver

    Feature Request: HTTP-Early-Hints header

    Why switching to other web server? If you already have <link rel="preload" ....> in your page just use CF Early Hints with 1 click.
  2. serpent_driver

    Mobile Theme Cache

    Did you read this? https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/
  3. serpent_driver

    Magento 2 installation with Varnish + Litemage?

    Yes, LiteSpeed or LSWS is a web server, but nothing else.
  4. serpent_driver

    Magento 2 installation with Varnish + Litemage?

    Installation is different so follow installation of each advicement.
  5. serpent_driver

    Magento 2 installation with Varnish + Litemage?

    There is no special way or method. Varnish is a page cache for HTML output and Redis is a MySQL cache, so there is no need for special adjustment to work each cache, but Redis is obsolete if a page is already cached. You can use Redis indepentently if any other page cache used.
  6. serpent_driver

    Magento 2 installation with Varnish + Litemage?

    You can use LiteMage and Redis, but LiteMage and Varnish will cause conflicts. Two page caches don't double the page cache benefits. Use LiteCache instead and double the speed of LiteSpeed: https://www.cachecrawler.com/LiteCache:::39.html
  7. serpent_driver

    Litespeed not start

    The error messages displayed encourage one to assume that LSWS has actually been installed?! Please raise a ticket at support@support@litespeedtech.com
  8. serpent_driver

    Feature Request: HTTP-Early-Hints header

    Still not possible, but if you have CloudFlare you can use CF Early Hints speed feature.
  9. serpent_driver

    Problem with svg files growing in size. Please help

    LiteSpeed Cache plugin doesn't support svg images because these image type is not an image, its's a document, so any advicements to this issue are obsolete.
  10. serpent_driver

    Litespeed issue with wp Travel Engine and/or elementor

    You should read before you post: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/
  11. serpent_driver

    How can one detect mod_env compatibility in LiteSpeed

    This forum provides you with support related to LiteSpeed Enterprise. If you have OLS then please use OLS support forum. There is no universal solution.
  12. serpent_driver

    How can one detect mod_env compatibility in LiteSpeed

    Again, if you have LiteSpeed Enterprise and not OpenLiteSpeed this script works.
  13. serpent_driver

    How can one detect mod_env compatibility in LiteSpeed

    The script also works with LiteSpeed web server.
  14. serpent_driver

    How can one detect mod_env compatibility in LiteSpeed

    Try this: if (function_exists('apache_get_modules')) { $modules = apache_get_modules(); $module_name = 'mod_env'; if (in_array($module_name, $modules)) { echo "$module_name is loaded."; } else { echo "$module_name is not loaded."; } } else { echo "Function...
  15. serpent_driver

    deploying Node.js on litespeed

    cPanel or CyberPanel? cPanel is not CyberPanel! LiteSpeed Enterprise or OpenLiteSpeed?
  16. serpent_driver

    https redirection not working

    Oh man, this is the reason why all the code doesn't work. cPanel can't be used with OLS! Please use OLS support forum for help. This forum is for LiteSpeed Enterprise only! https://forum.openlitespeed.org/
  17. serpent_driver

    https redirection not working

    This question is actually redundant, but just to be sure, you are using LSWS and not OLS?
  18. serpent_driver

    https redirection not working

    Contact cPanel support. There is something wrong with your cPanel configuration.
  19. serpent_driver

    https redirection not working

    You said that if you enter http://example.com it doesn't redirect to https://example.com, right? Where does it redirect to?
  20. serpent_driver

    https redirection not working

    You must add this code to .htaccess and not to the conf file and replace example.com with the domain name used. RewriteCond %{SERVER_PORT} !^443$ RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L] RewriteCond %{HTTP_HOST} ^www\. RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]
Top