shu
March 30, 2023, 5:22pm
1
Site link: textcompare.netlify.app
This is a nextjs app.
If you check the headers there is vary: X-Bb-Conditions,Accept-Encoding
header present.
I’m trying to find out why and where this header is being sent?
Can it be removed? (this header is messing up caching in cloudflare)
Why are you caching with Cloudflare? Netlify serves sites via a CDN with a cache.
Here are some relevant support guides
Last reviewed by Netlify Support on August 2023
While the topic of caching effectively is complex, Netlify’s solution is designed to be automatic and worry-free. It shouldn’t require any special configuration or build tools like cache-busting or service workers to deliver an optimal experience.
What can go wrong?
Some cache-busting techniques can make your site build and load more slowly. Scarier still, modifying Netlify’s default caching settings can break atomic rollbacks and deploys , which…
Last reviewed by Netlify Support - August, 2023
Our CDN derives much of its efficiency from files whose checksums don’t change between deploys.
For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to …
Last reviewed by Netlify Support - August, 2023
Note: We recommend not using both Cloudflare’s CDN (“Accelerate and Protect”, the orange cloud in their UI) and Netlify for the same site at the same time. Why? Read on!
Netlify’s web service is not designed to work optimally with another CDN “in front of” our CDN. Proxying to our service is in general not supported and we advise you not to do it for best hosting results.
Cloudflare has made similar statements that it doesn’t recommend this usa…
shu
April 8, 2023, 6:00pm
3
Why are you caching with Cloudflare? Netlify serves sites via a CDN with a cache.
The site is monetized by Ezoic which in turn uses cloudflare for their setup.
That’s a system-level header used for some purposes and cannot be removed. A lot of users use Cloudflare in front of Netlify and no one has complained about it, so there must be some configuration specific to your case that’s causing issues.
shu
April 16, 2023, 12:15pm
5
unusual header caused ezoic to stop caching request.
ignoring the header fixed the issue.