Search results

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...

@KratosGemini Basically, there is no need to delete the /lscache directory manually. LScache has a self-cleaning function that automatically deletes all cache files. However, only for these cache files whose lifetime has expired. Caches of URLs that have been manually purged are not affected...

Wordfence has a misunderstanding of what noabort means. This directive is intended to prevent user abort. Wordfence wants to regulate the timeout, but somehow it doesn't want to get into Wordfence's heads. Also, Wordfence's recommended use of the noabort directive poses a security risk, but...

@AndreyPopov If it works with OLS, then that seems fine, but keep in mind that this setting applies to all scripts and is therefore a security risk. But I doubt that this setting works in all cases.

@Cold-Egg I tested the noabort and noconntimeout directives with the LSWS and OLS in different scenarios. It works, but not in every case and depends on the PHP processes or child processes. An example of this would be a script that converts images using Imagick. In this case it doesn't work.

@Cold-Egg Will test it, thank you!

@Cold-Egg That's very strange. No matter what attempts I read from numerous users, they all come to the conclusion that these directives do not work in OLS, so I can only conclude from your answer that it must be due to the type of script and process. Can you tell me how you tested this?

These directives are unsupported in OLS. Only max_execution_time works in this case with OLS.

Sorry, you are wrong. I have developed a cache plugin for Shopware 5 and it works with OLS. The plugin you link to is not a LiteSpeed plugin, just a third party "service". You can't get the plugin from this provider and you can't buy it either. This is not an OLS issue, but a question of the...

If you run not just one, but several WooCommerce sites, then you are inevitably bound to the purge behavior of the cache plugin. This inevitably means that in the event of a product update, not only the cache of the product page, but also the cache of the categories will be purged. This is still...