The W3C estimate instantly below will make crystal clear that this isn't the case; rather, the no-cache header just signifies that the response should be revalidated ahead of getting reused to serve subsequent requests. It absolutely was supposed like a privateness evaluate: it tells browsers and caches the reaction has https://sociallweb.com/story6501912/not-known-facts-about-%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