Hi @Jan ,
when we disable Cloudflare completely, the gz file will be cached by Ezoic and get HIT. We have set it for the whole website including the /static folder according to Ezoic guidelines which is for our case "Standard" https://support.ezoic.com/kb/article/cloudflare-page-rules-and-ezoic
BUT - the whole website is integrated with Cloudflare and everything is set to "Standard" - So all pages are cached initially by Cloudflare. Ezoic acts always as top cache layer and works for the full website and all assets except gz files.
All pages and assets will therefore get a DYNAMIC from Cloudfare and a HIT from Ezoic. You can test it on each and every page and on each asset like here: https://staging.theworldtravelindex.com/static/filters/96b298e156d1587394b1b97c9eb683dd.json
The question is - why gz files like this https://staging.theworldtravelindex.com/static/filters/abc.json.gz are not getting cached from Ezoic. I understand because CF will show HIT. And it shows HIT because Ezoic is not caching it. What we don't understand why all assets and all pages with same Caching Rule "Standard" will work, but these gz files will not work unless Cloudflare is completely disabled.
We already tested with htaccess and without htaccess rule. This is not the culprit.
You can test in your own sandbox, gzipped json files with Cloudflare set to standard. Most likely you will see the same - Cloudflare will HIT, and Ezoic will be MISS on such assets, while all other assets and pages will be Cloudflare = DYNAMIC and Ezoic will be MISS.
We did now a workaround to make gz files work for Ezoic. Only when a specific page rule is in place which explicitly says "Bypass" it will work:
You might want to investigate or fix this issue for gz files (when "Standard" is used) or put a technical note in your docs, that "gz files" need a dedicated "bypass" rule in Cloudflare in order to get cached by Ezoic CDN.
Thanks