I have a php file, and after hours of troubleshooting to figure out why after I turned over things to cloudflare my page (rendered from said php file) wasn’t responding correctly anymore, I positively was able to establish that even though I have headers explicitly set up to no-cache in the file, cloudflare still cached the resource! And I did not have any page rule set up to override what I explicitly requested in the headers.
I don’t need a reply that tells me “oh, maybe you didn’t do this, maybe you didn’t that, blah blah blah…” because I am positively telling you that cloudflare cached my php file whereas the header said not to cache it. I am very sure that something is wrong on the cloudflare side, and I want to know why cloudflare is so aggressive in caching even resources that have been marked to not be cached, please give me an answer to that, why??? Why???
Please don’t reply to my question with more questions, if you don’t know the answer then please don’t reply.
Cloudflare is caching resources it was asked to stay off of, and I want to know why this is the case and how to stop it, because it essentially means cloudflare is not doing what it claims in its documentation. I read all the caching docs on cloudflare I could find, and this behavior is not supposed to happen; this is very fishy.