![]() ![]() You can always choose not to provide us with the requested information, however, you may not be able to complete the transaction or use our products or services if you do not provide the information requested. LiteSpeed will ask you for certain “Personal Information” when you complete registration or product information request forms on the Site, including but not limited to your name, address, telephone number, email address, and credit card information. IF YOU DO NOT AGREE WITH ANY OF THE TERMS BELOW, YOU SHOULD NOT USE THIS SITE OR THE PRODUCTS OR SERVICES OFFERED BY LITESPEED TECHNOLOGIES AT THIS SITE. LiteSpeed encourages you to review this Privacy Policy periodically for any changes. If we make changes to this Privacy Policy, we will update the Effective Date to note the date of such changes. LiteSpeed reserves the right to revise, modify, add, or remove provisions to this Privacy Policy at any time. By using this Site or any products or services provided through the Site, you expressly consent to the use and disclosure of information as described in this Privacy Policy. You can visit most pages of the Site without giving us any information about yourself, but sometimes we do need information to provide services that you request. This policy ("Privacy Policy" or "Policy") explains our practices for our site, ("Site"). (aka “LiteSpeed”) is committed to protecting your privacy. Easily run multiple versions of PHP on one server.Most up-to-date high performance HTTP/3 implementationr.Support Ruby/Python/Nodejs Applications with native configuration.Virtual host templates for easy configuration.Control panel plugins (cPanel, DirectAdmin, and Plesk).Dynamic vhost setup through Redis backend or Rewrite Rules.Drop-in Apache replacement for cPanel, Plesk, DirectAdmin, Interworx, etc.Reads Apache's configuration files directly.Recovers from service failure instantly.High Availability for Redis Dynamic vHost Setup.CPU affinity allows for greater use of CPU cache.Just in time configuration cuts restart time.Separation of server and web applications allows for buffering of requests and responses, leading to better handling of multiple connections.Increases scalability of web applications.htaccess caching removes performance bottlenecks associated with. Turbocharge Magento and other web applications with ESI support.Dynamic content up to 40x faster than Apache.Static content up to 5x faster than Apache.Three different PHP suEXEC setups for different needs and abilities.Unrivaled PHP suEXEC performance for shared hosting. ![]() LiteSpeed's exclusive server API (LSAPI) delivers the best dynamic content performance.Unbeatable HTTPS performance with TLS record level optimization.HTTPS / TLSv1.3 certificate compression.Hundreds of thousands of concurrent connections.External application and full server chroot ability.Anti SSL BEAST and renegotiation attack capabilities.Compatibility with Atomic Secured Linux and Atomicorp Realtime ModSecurity Rules.Built-in anti-DDoS connection and bandwidth throttling.Brute-force protection for wp-login.php.Session tickets with automatic key rotation for forward secrecy.Server-Level ReCaptcha layer-7 DDoS attacks Protection.Runs on Linux, FreeBSD, MacOSX, Solaris.Unlimited IP and name-based virtual hosting.Server APIs: LiteSpeed SAPI (LSAPI), CGI, FCGI, AJPv13, Proxy.Scripting Languages: PHP, Perl, Ruby, Python, Java, etc.We know that WordPress has a CF module which enables CF and LiteSpeed's cache module to work simultaneously. ![]() Somehow there is a conflict between CF and LiteSpeed in this setup which causes the redirect error. We have tried to disable the LiteSpeed cache module again (the LiteSpeed's rewrite rules are of course still unchanged even though the cache module has been disabled in PS) - and the issue remains. We believe it's due to Litespeed's re-write logic. The page just redirects to itself again and doesn't complain about wrong user credentials or similar. Screenshot of the test-domain which is not "proxied" via CF: When we disable "proxied" in CF then we can login via the PS Admin page again as seen in the screenshot below:.Screenshots of the main-domain which is "proxied" via CF: ![]() All other functionality on the site works flawless. It looks like the login page is called 2 times in a row. We have migrated a PrestaShop(PS) v.1.7.8.7 from an Apache server to a LiteSpeed server which includes the LiteSpeed cache module for PS and crawler enabled.ĬloudFlare(CF) has always been in play with both the existing and the new server.īut when we enable "proxied" in DNS settings for the new server - then we suddenly can't login at the admin URL due to a 302 error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |