Search results

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

There is a very simple but extremely effective method for distinguishing bots or "natural" requests from "unnatural" requests. This requires neither complex programming nor any external service. If anyone is interested in it, I'll write a documentary about it here in the forum.

It would be nice if you could do it the way you suggest. However, you seem to lack the relevant knowledge. The problem that the cache has to be purged affects WooCommerce users in particular, but not only. Products in a shop, their information about them and their status are not limited to the...

https://goldenmoments.sg/media wrong, but if requested it should redirect to https://goldenmoments.sg/media/ https://goldenmoments.sg/media/ right There must be a no-cache rule either in the plugin or in the .htaccess. Check your plugin settings, but I advice you to reset to default settings...

Check your .htaccess. There is something wrong. https://goldenmoments.sg/media can also accessed by https://goldenmoments.sg/media/ https://goldenmoments.sg/blog can also accessed by https://goldenmoments.sg/blog/ Both URLs without redirection but they should be redirected...

What about CloudFlare cache?

Does that help you? https://forum.openlitespeed.org/threads/uri-refers-to-a-static-file-with-path_info-error.5440/

@et_goldenm Run "Purge All - CSS/JS Cache" This kind of purge should solve the issue.

@mikegs1 You've obviously made a lot of effort, but you can save 2/3 of this work because it's unnecessary. Especially since every rewrite rule does not make your server faster and safer. Most of these rules are therefore meaningless. I cannot recommend other interested readers to adopt these...

It's primarily about Wordpress or the LScache Plugin (LSCWP) for Wordpress, but the problem affects every LiteSpeed Cache Plugin for which a Cache Warmup Crawler is available. In order to benefit from LScache, it is imperative that the cache is warmed up. If you don't do that or maybe don't...

If statistics are to be believed, there is currently only 1 web server that has shown significant growth rates for more than 10 years. All others seem to have been weakening for quite some time. Where does that come from?

Ever since Google Pagespeed, there has been a misconception that Google doesn't really want to create despite sufficient criticism. But before I demonize Google, I want to first praise Google. Praise for the fact that Google has been the only authority for almost 20 years now, which is committed...

The following explanations should help to answer the basic question of what advantages and disadvantages there are by using a CDN and whether there are alternatives. Basically, a CDN follows the principle: "Bring content closer to the user". Leaving everything else aside, everyone should be...

And again and again, if you get 304 status code in your case and only in your case this is not a result of special settings. This is a absolute normal behaviour of every browser if he requests a static source that is not css, js or image. In your case index.html is a static source!