The W3C estimate quickly beneath tends to make distinct that it's not the situation; fairly, the no-cache header just means that the reaction has to be revalidated just before being reused to provide subsequent requests. I discovered the net.config route valuable (made an effort to insert it to The solution https://total-bookmark.com/story20840834/%E4%BB%AE%E6%83%B3%E9%80%9A%E8%B2%A8-%E3%82%AA%E3%83%B3%E3%83%A9%E3%82%A4%E3%83%B3%E3%82%AB%E3%82%B8%E3%83%8E-no-further-a-mystery