Hi @fakhrur,
Looking at the response header of your webpage, it seems that you are having this issue because you have some other caching system in place which is overwriting the cache-control header.
When the plugin is working properly you will see that the value of cache-control header and the x-wp-cf-super-cache-cache-control should match.
But as you can see they are not the same in this case. So, you might have some caching system (either some other caching plugin or server level caching solution) in place or some server rules that is adding the private, must-revalidate value.
So, basically you need to figure out who is adding the cache-control: private, must-revalidate rule as that’s what causing the page not to be cache as that cache control rule is telling Cloudflare system not to cache the webpage.
Ah, i see the problem, can you see what wrongs with my httacess, thanks.
Cache-Control Headers
Header set Cache-Control "public" Header set Cache-Control "public" Header set Cache-Control "private" Header set Cache-Control "private, must-revalidate"
Header set X-Content-Type-Options "nosniff"
Header set X-XSS-Protection "1; mode=block"
Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains"
php -- BEGIN cPanel-generated handler, do not edit
This domain inherits the “PHP” package.
php -- END cPanel-generated handler, do not edit
BEGIN WP Cloudflare Super Page Cache
Arahan (baris) antara "BEGIN WP Cloudflare Super Page Cache" dan "END WP Cloudflare Super Page Cache"
dihasilkan secara dinamis, dan hanya dapat dimodifikasi melalui filter WordPress.
Setiap perubahan pada arahan di antara penanda berikut akan ditimpa.
ExpiresActive on ExpiresByType application/xml "access plus 0 seconds" ExpiresByType text/xsl "access plus 0 seconds"
Header set Cache-Control "no-cache, no-store, must-revalidate, max-age=0"
Header set Cache-Control "no-cache, no-store, must-revalidate, max-age=0"
Header set Cache-Control "public, must-revalidate, proxy-revalidate, immutable, max-age=2592000, stale-while-revalidate=86400, stale-if-error=604800"
Header set Cache-Control "public, must-revalidate, proxy-revalidate, immutable, max-age=31536000, stale-while-revalidate=86400, stale-if-error=604800"
RewriteCond %{REQUEST_URI} ^(.)?/wp-content/wp-cloudflare-super-page-cache/fakhrurpedia.com/debug.log(.)$ RewriteRule ^(.*)$ - [F]
Header set Cache-Control "no-cache, no-store, must-revalidate, max-age=0"
END WP Cloudflare Super Page Cache
Hi @fakhrur,
Can you remove the following line from your htaccess file?
Header set Cache-Control "public" Header set Cache-Control "public" Header set Cache-Control "private" Header set Cache-Control "private, must-revalidate"
already deleted sir, can you inspect more?
Hi @fakhrur,
As I can see caching is working perfectly on your website now.
Also you should consider enabling this option for adding better cache-control header for the static files.
already set-up browser cache sir, is this correct settings?
https://prnt.sc/OG8ACrv4WRaB
Yup, All working good:
You should also enable smart tiered cache inside your Cloudflare Dashboard.
After that inside the plugin settings > others tab scroll down to the end and check the Remove Cache Buster Query String option. Read the implementation guide link given there. Follow the instruction guide.
Smart tiered cache & Remove Cache Buster Query String what i got from these feature sir? Can you give me reference about 2 feature you give, thanks
Smart tiered cache will increase your cache HIT ratio. Remove query string with cache rules will help you get rid of the ?swcfpc=1 cache buster query param and also help increasing your caching HIT ratio but ignoring the unnecessary query strings.
ah i understand sir, thank you very much for tips, i will marked this issue resolved