The W3C quotation straight away down below will make very clear that this isn't the case; rather, the no-cache header just means that the response have to be revalidated ahead of being reused to serve subsequent requests. I edited configuration file of my challenge to append no-cache headers, but that https://total-bookmark.com/story20838989/little-known-facts-about-%E4%BB%AE%E6%83%B3%E9%80%9A%E8%B2%A8-%E3%82%AB%E3%82%B8%E3%83%8E-%E3%82%B3%E3%82%A4%E3%83%B3