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?