Search results

If I check response header of this plugin I can see "hit" value for cache header, so it seems still to work.....

What about your NitroPack cache plugin. Do you use it together with LScache plugin?

Try Slack instead of Ticket Support: https://www.litespeedtech.com/slack or send mail to: support@litespeedtech.com

Copy and paste to your .htaccess. This (should ) disable cache for logged in users. RewriteCond %{HTTP_COOKIE} _lscache_vary=session:loggedIn [NC] RewriteRule .* - [E=Cache-Control:no-cache] If it doesn't work log a ticket to get support from LiteSpeed support.

This is all the result of what goes wrong with AJAX login. Much better, so please wait.

Hm, this cookie has logged out value. You do have to login and check cookies again and post it.

Okay, the affected cookies name is _ls_cache_vary, so wait a few minutes to make the code for it.

This for device detection only and is something complete different to your issue. But you know what the F12 key is.....?

No need to know about OpenCart. Login to your shop and request a page that isn't cached. Press F12 key and check the tab for cookies. The name of the tab for cookies depends on browser.

Lscache is able to do that, but the cache plugin can't. It needs an extra menue in the GUI.

If you tell me the name of the login cookie, it can be done very easy.

This is a complete normal behaviour with every cache, not only LScache. If a page is cached there is no more PHP, only HTML and if no PHP there is no session. And if no session a user can't be differentiated form each other. To prevent this disadvantage of every cache LScache uses cache varies...

This popup seems to use AJAX and the trick of AJAX is not to refresh the complete page and not to load the complete page again. But LScache engine needs a refresh to check if the login cookie is set to vary the cache. At this moment and to me I can't see any other solution as to use...

Would you provide us with the error?

Have you already asked Hetzner Support? For me, this would be the first contact point....

Sorry to choose german.... There is no known reason why LiteSpeed should limit transfer rate and also don't know how that could be done. I am also at Leaseweb with datacenter in Frankfurt, but never had any problems with transfer rate with LiteSpeed in the last 10 years.

Identische Konditionen. Was also ist das Problem? Allerdings weiß ich nicht, was Du mit Rescue Mode meinst?

After update to 5.4.11 (build 4) WebAdmin displays warning: Warn [6679] [SSLTicket] ticketCb() SHM keys need rotation Anything to be done on my side?

What about the simplest reason? Your hosting provider limits the speed.

IE11 needs TLSv1.1 https://docs.litespeedtech.com/cp/cpanel/tunings/#customize-ssl-ciphers