Search results

You can only actually debug the problem if you have ruled out all conceivable sources of interference and that inevitably includes the CDN. Even if you have solved the login problem, there are still much bigger problems that are even more difficult to solve. So I just ask you one question...

You need private cache for logged-in users. This is important, otherwise you will get new issues. Not logged-in users will see cached content from logged-in users, you understand?

The code for the .htaccess is logically correct and meets all the necessary requirements. However, I don't know the PHP code of your site, so it may well be that you either have to change or add something. This primarily concerns that the cookies are set correctly.

That would be a conceivable reason! Can you temporarily disable the CDN?

No, this is not a rewrite rule and will not work with OLS. https://openlitespeed.org/kb/how-to-set-up-custom-headers/

<IfModule litespeed> CacheLookup on RewriteEngine On RewriteCond %{REQUEST_URI} ^/admin/ [NC] RewriteRule .* - [E=Cache-Control:no-cache] RewriteRule .* - [E=cache-control:max-age=120] RewriteCond %{HTTP_COOKIE} set_cookie_login_name [NC] RewriteRule .* - [E=cache-control::private,max-age=120]...

For dynamically generated documents: For OLS please set accordingly! <FilesMatch "(\.html|\.htm|\.php|\.HTML|\.HTM|\.PHP)$"> Header set cache-control: private, no-store, no-cache, must-revlidate </FilesMatch>

Please post cache-control (not x-litespeed-cache-control) settings. If you offer different languages you need a language cookie with different values depending on selected language. Then you can define a cache vary depending on cookie value.

Try this: <IfModule litespeed> CacheLookup on RewriteEngine On RewriteCond %{REQUEST_URI} ^/admin/ [NC] RewriteRule .* - [E=Cache-Control:no-cache] RewriteCond %{HTTP_COOKIE} set_cookie_login_name [NC] RewriteRule .* - [E=cache-control::private,max-age=120] RewriteRule .* -...

POST is set to no-cache by design, so there must be other reason that causes this issue. Do you use AJAX for login? Do you set any cookie for login?

Which request method do you use for login? POST or GET?

Therefore it is smarter not to use UCSS inline. It is even smarter to use UCSS as Critical CSS, because only CCSS actually improves the loading time. In addition, it consumes significantly less storage space and the storage size of the main document is only slightly larger.

@krrish Why do you use private cache with your page?

CSS, JS, images and so on are static sources and such sources are cached by the browser and cannot cached by OLS. The browser needs such sources to be cached, not the server.

This doesn't matter, because nobody asked for to cache only particular content. Especially since this question does not even arise with OLS. It's only about to make cache available without any plugin. Rewrite Engine is always enabled and there is no need to point this out specifically. Please...

@AndreyPopov You do not improve your reputation by repeating previous posts. Therefore, fill us with knowledge that we do not yet know.

There is nothing special to run LScache without a plugin, but a cache plugin makes it easier to handle it. Just add this to your htaccess. <IfModule LiteSpeed> CacheLookup on RewriteRule .* - [E=cache-control:max-age=[time in seconds] </IfModule> That's it, but you have to define more cache...

This is not a rewrite rule, so please follow the advice of @Cold-Egg

@bayardo.rivas With my code suggestion you don't need WP backend access. It's a LiteSpeed and PHP native method and you can choose which cache of which site should be purged.

If you don't want to call up every LSCWP installation to purge the cache, there is also a quick and native solution for this. Note, however, that the following solution, like deleting the cache via LSCWP, does not delete the cache files. Empty /lscache dir rm -Rf /lscache Purge cache by...