Search results

Remove this from your .htacces or the aff* cookies. ### marker NOCACHE COOKIES start ### RewriteCond %{HTTP_COOKIE} affwp_ref|affwp_ref_visit_id|affwp_campaign|wptouch_switch_toggle|wp\-affwp_ref_visit_id|wp\-affwp_ref|wp\-affwp_campaign RewriteRule .* - [E=Cache-Control:no-cache] ### marker...

You have quic.cloud running and QC doesn't know about this no-cache rule. Please purge the cache, wait some minutes and try again.

I have just tested it at my test page and it works as expected. Where did you place the code?

Does not cache? This is what you wanted?!

For single referrer: <IfModule LiteSpeed> RewriteCond %{HTTP_REFERER} domain\.com [NC] RewriteRule .* - [E=Cache-Control:no-cache] </IfModule> For multiple referrer: <IfModule LiteSpeed> RewriteCond %{HTTP_REFERER} domain\.com [NC,OR] RewriteCond %{HTTP_REFERER}...

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

You can define a rewrite rule in .htaccess. If request has referrer and if referrer has a specific name, then you can disable caching for this request. This works with any URL at your page.

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

You are using quic.cloud and it seems that QC doesn't honor cookie exclude rules in .htaccess. Otherwise all URLs would be excluded from caching if any of these affiliate cookies is set. The URL to test affiliate link is not cached, but not because of the cookie, but this URL seems to be...

Check error_log. It seems not to be a LSPHP issue, but an issue of unsufficient PHP configuration. Check allow_url_fopen.

btw. if you have cache plugin for Wordpress running, just use the crawler to warmup the cache for URLs in short time periode..

If you see x-qc-cache header then this request goes to quic.cloud and not to your server. If this header has hit value then the requested URL is already cached and there is nothing more to do or you can do, but the best is you use LiteSpeed web server instead of Apache.

Yes and no. If a URL isn't cached/copied by QC and you see a "x-litespeed-cache" header, then this is the response cache status header of your server. QC has "x-qc-cache header" miss or hit.

Yes, it worked, but with LScache plugin the case looks quite different and you can't compare the current case with LScache plugin with earlier case without cache plugin. If a page isn't cached and still isn't optimized the load (not the CPU load) is as doubled. LiteSpeed already knows about...

@leekle In order to determine the load on a server, it is not enough just to check the CPU load. It's about the so-called SysLoadAverage and it takes into account all the factors that can affect the load. Regardless of that, and at least you know that, the cache plugin for Wordpress is a...

Sorry to say that, but your VPS isn't strong enough. 2 "virtual" CPU and 2 "virtual" GB isn't enough to run Wordpress. You should take a closer look at your load. For this I recommend PhpSysInfo to check what is going on on your server. https://phpsysinfo.github.io/phpsysinfo/

You are using a "stupid" crawler script. Stupid means it doesn't care about the load and anything else, because it hasn't any kind of detection that can detect the load. That basically is the reason why you could you get this error message. In specific case with requests from Googlebot...

Any CDN is only as good/fast as the CDN has the content cached/copied. If it isn't cached or copied the request goes to the origin (your host) host. This this the basical prinzip of any CDN regardless of quic.cloud, so whenever you check the speed at GtMetrix or any other pages for testing you...

Basically if you have cache plugin for Wordpress installed, please use Wordpress support page for WP cache plugin. This forum doesn't support cache plugin for Wordpress any longer. https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/ If you have...

@leekle FYI: Cache plugin for Wordpress is known as a perfomance killer, atleast a page isn't cached|optimized. It causes a higer load due database requests. This especailly happens if the build-in crawler is executed, but the load depends on your plugin settings. The more you enable the higher...