AnsweredAssumed Answered

No-Store for 302s

Question asked by Geoff McGill Employee on Aug 2, 2016
Latest reply on Nov 15, 2017 by Gunther Kochmann

What is the best way to make it so that 302s are not cached? From reading the docs it sounds like if origin doesn't send a cache-control header or an expires header then it's considered not cacheable, are there any other ways to do this? For example, if the origin sends cache-control: no-store?


If the origin is sending a cache-control header on 302s making them cacheable, can it be overridden in the config somehow, for example using the behavior to remove incoming response header?