Oh damn... I've seen this one too. As always this is doing REST api without understanding the nuances of http and its headers. The application service in this c

Oh damn... I've seen this one too. As always this is doing REST api without understanding the nuances of http and its headers. The application service in this case wasn't setting the correct cache-control. A proxy some layers above happily cached it. Adding the cache-control didn't make a difference. The proxy had to be restarted (the cache was within its ttl so didn't get changed). Ideally an api gateway should have managed the headers but ours didn't. Not at that time at least.