The W3C estimate instantly below makes obvious that this is not the situation; rather, the no-cache header just means that the reaction have to be revalidated just before becoming reused to serve subsequent requests. I discovered the internet.config route helpful (made an effort to add it to The solution but https://esocialmall.com/story6442671/%E3%82%AA%E3%83%B3%E3%83%A9%E3%82%A4%E3%83%B3%E3%82%AB%E3%82%B8%E3%83%8E-%E4%BB%AE%E6%83%B3%E9%80%9A%E8%B2%A8-secrets