The W3C quote immediately below will make apparent that it's not the case; fairly, the no-cache header just implies that the response must be revalidated right before remaining reused to serve subsequent requests. If the no-cache directive isn't going to specify a area-name, then a cache Need to NOT make https://bookmarksystem.com/story20800698/an-unbiased-view-of-%E3%82%AA%E3%83%B3%E3%83%A9%E3%82%A4%E3%83%B3%E3%82%AB%E3%82%B8%E3%83%8E-%E3%83%93%E3%83%83%E3%83%88%E3%82%B3%E3%82%A4%E3%83%B3