Earlier quoted context omitted.
the same happens for all browsers, Chrome, Safari, Firefox with default settings. but do agree this is not normal behavior :/ actually caching is happening, but it does not follow ETags or Caching policy headers that backends return, instead some in-browser internal caching policy being run
I’ve never seen the behavior you are describing. I would check that you’re sending the headers correctly: https://neilmadden.blog/2020/05/18/a-flowchart-for-cache-con... I’ve used that flowchart too many times.
yep, I tried countless variations of this while testing. did not work!
my conclusion in the end, this was intentional by browsers. they give priority to the their internal caching policies for performance or user-experience :/