how do you know that the edge cache and the worker do not work because of the header?
Simple testing. Here are the steps to replicate:
1
Redbot.net outputs the errors and highlights the headers causing the errors.
2
Tested by removing that section of .htaccess code.
3
Redbot indicates Cloudflare “Hit”
4
Then pressed “save” on WP-Fastest cache settings.
5
Reloaded .htaccess and that section of .htaccess code has been added back in by WP-Fastest cache.
6
Redbot flags errors and indicates Cloudflare “Bypass”.
7
Our current workaround is to 444 .htaccess to prevent WP-Fastest cache adding the section of headers.
————–
Output from rebot.net:
Cache-Control: private, must-revalidate
Expires: Mon, 29 Oct 1923 20:30:00 GMT
Last-Modified: Sat, 25 Jul 2020 13:02:06 GMT
Strict-Transport-Security: max-age=15552000
Vary: User-Agent,Accept-Encoding
CF-Cache-Status: BYPASS
cf-request-id: 0427aa35db000004c081b18200000001
Expect-CT: max-age=604800, report-uri=”https://report-
uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
Pragma: no-cache
Server: cloudflare
The header is used to disable the browser cache for html files. it does not block cloudflare.
you need to add a rule via “Page Rules” as below.
https://i.ibb.co/wRkKLWk/Screen-Shot-2020-07-25-at-17-23-03.png
We already use page rules and workers. That is not the issue here.
With respect, the issue is with the deprecated Pragma code your plugin adds to .htaccess
I would urge you to test and replicate.
Nevermind. I will rewrite your plugin and fix it myself.
Any movement on this? I have to rewrite the plugin each time it updates! Why do you still use deprecated pragma headers??
