When our application goes behind the Cloudflare CDN we the header eTag gets affected.
Not through Cloudflare (observed valid header):
Through Cloudflare (observed invalid/amended header):
Article like this ( https://support.cloudflare.com/hc/en-us/articles/218505467-Does-CloudFlare-support-ETag-headers- ) does not help.
Even a Rule that sets cache to Bypass and disables all Cloudflare apps does not help.
With CloudFront CDN (AWS) as an example this is controlled with behaviour very well. We are very surprised it doesn’t with Cloudflare.
Has anyone had this pain before and managed to solve it?
From the link above:
When using weak ETag headers, disable Email Obfuscation and Automatic HTTPS Rewrites to ensure Cloudflare doesn’t remove the ETag headers set by your origin web server.
Just to conclude, Cloudflare Apps is not the same as options (or features which we can enable) like Email obfuscation, Automatic HTTPS Rewrites, Rocket Loader rather Apps from the Cloudflare App Center as follows on the link below:
I am sending ETag for resources like images, CSS, JS from my origin host/server, but using
Origin Cache Control in a Page Rule (including
Cache Level: Cache Everything).
The thing is, Cloudflare doesn’t remove the ETag headers set by our origin web server, it changes it. I’ve tried to disable Email Obfuscation and Automatic HTTPS Rewrites but those had no effect… Cloudflare was still interfering with the eTag.
Having the same problem.
My server is sending back an e-tag and Cloudflare is overwriting it with another e-tag. How to disable this functionality?
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.