We had a big problem on our web service last couple hours!
It looks like Cloudflare have changed the default Cache-Control headers!
It became - cache-control: private, max-age=14400, must-revalidate
So, every “GET” ajax queries to dynamic data started caching!!
This led to the application’s fatal work.
Can anyone confirm changes to the default headers of Cloudflare?
I thought I was going crazy! This also has happened to our website and is ruining everything!!
I confirmed it was Cloudflare because I changed the Cache Time and saw it updated.
I managed to workaround this by setting this to Respect Headers.
This setting hasn’t changed in 5 years (prior to me just changing it).
The issue is that Cloudflare is not supposed to cache HTML content but it is (as seen above).
I have this issue too, my CMS page is now being crazy. New HTML content never updates if I don’t refresh browser several times to see change, I don’t know what to do now and I have to turn off the Orange-Cloud in DNS section.
I have tried, it didn’t help. As budgeneration has wrote, you can switсh to “Respect Headers” and setup correct headers on your web server. or add Pragma: no-cache until there is news on the issue.
I confirm we’ve just had the same problem. Seems CF are now inserting cache-control: private, max-age=14400 on all our api requests too.
I’ve just changed the same Browser Cache Expiration to Respect Existing Headers too, as our api was sending cache-control: no-cache. Now it seems to be working again.
How/why did this change? What a massive change!