Search results

Okay, then you should check which kind of URLs are generated or did you already checked it?

I don't know if can go shure. I only see your code. Maybe I am wrong or I overlooked the SEO part. Nevertheless, if there are SEO URLs add the single curl parameter for to CURLOPT_NOBODY to reduce request times.

And this the "magic" behind https://check.lscache.io wget -q -S -O - "https://www.priazha-shop.com" > /dev/null or with curl curl -D - https://www.priazha-shop.com -o /dev/null

So Mr. Super Warmup Cache Crawler Master, below you will see what is wrong with your code and your super deluxe recache warmup script. The first code is the default code taken from lscache module for Opencart, but modified by Mr. Super Warmup Cache Crawler Master with Accept Encoding Header...

If client (curl) sends "Accept-Encoding: gzip,deflate,br" request header, LScache will compress cache files, but this compression is different to compression for data transfer compression, so it doesn't matter if you use gzip, deflate or br. Cache file compression is always the same, but if you...

All codes you tried from above are working codes. There is nothing special on it. If they do not work at your server something must be wrong with domain and subdomain configuration. Check if subdomains and .tld domain have same document_root.

What if you only set a redirection without any condition, but that expects that each subdomain has its own document_root? RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]

You could post your .htaccess?

If you have OLS any changes in .htaccess will only apply if OLS has been restarted!

Try this: RewriteCond %{HTTP_HOST} !^example\.com$ [NC] RewriteRule ^(.*)$ https://example.com/$1 [L,R=301,QSA] Place it on top of .htaccess. If you have OLS instead of LSWS you must restart OLS to apply changes.

@LuigiMdg Why don't you do what I suggested? It does exactly what you want to get! https://www.litespeedtech.com/support/forum/threads/purge-cache-at-00-oclock.20713/post-119895

You have rewrite rules in your .htacess that come from other cache plugins and these rules affects queries in URL, so you have to clean and reset it to default .htaccess. Otherwise there is no way to find a solution. Use Wordpress default .htaccess and remove anything else. If done and if you...

Still only Nonsense!

The one who can read always win. :) https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

@AndreyPopov As long you don't respect people who have much experience and knowledge about curl and other LiteSpeed related stuff you will never really improve anything. Your current published code about how to improve crawling and caching is bullshit. You do a lot and if it works you don't...

Nonsense! If the client doesn't send any information about if he supports any compression how should the server know if he can compress traffic? Why are the cache files sizes are so big? Right, because server hasn't compressed it due unknown Accept parameter HTTP/2 is only used by curl if...

If you have Wordpress then you will get support for Wordpress cache plugin at Wordpress plugin support. This forum no longer offers support for cache plugin. https://wordpress.org/support/plugin/litespeed-cache/

I adviced you to set the new code "on Top" of .htaccess. Where does the question mark come from? To solve your issue the best solution is to remove the reason why this question mark is set!

curl_setopt($ch, CURLOPT_ENCODING, ""); Means neither traffic will compressed nor the cache will be compressed and if there is no compression much more disk space is needed => a logical result. And a further result it is that LSWS or OLS creates compressed copies of the cache files next time...

@Defacto Almost all settings in LSWS WebAdmin are for native use of LSWS if there is no control panel! That's why you don't see any virtual hosts.