The W3C quotation straight away underneath can make obvious that it's not the situation; alternatively, the no-cache header just ensures that the reaction needs to be revalidated right before getting reused to serve subsequent requests. I edited configuration file of my venture to append no-cache headers, but that also disabled https://kingslists.com/story22338212/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