The W3C quote instantly below makes apparent that this is simply not the case; alternatively, the no-cache header just signifies that the response needs to be revalidated in advance of getting reused to provide subsequent requests. I discovered the net.config route handy (attempted to add it to The solution but https://bookmarkingdepot.com/story20915502/how-much-you-need-to-expect-you-ll-pay-for-a-good-%E3%82%AB%E3%82%B8%E3%83%8E-%E4%BB%AE%E6%83%B3%E9%80%9A%E8%B2%A8