The W3C quotation promptly underneath can make very clear that this isn't the case; relatively, the no-cache header just ensures that the reaction should be revalidated before staying reused to provide subsequent requests. It absolutely was meant being a privacy evaluate: it tells browsers and caches that the reaction includes https://ledbookmark.com/story6727466/the-single-best-strategy-to-use-for-%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