A response from a Cisco health API includes Cache-Control: no-cache. What does that directive mean for the consumer’s stored copy?
Select an answer to reveal the explanation.
Short Explanation
no-cache is “show your ticket again before you sit,” not “throw the ticket away.” You may keep a copy, but revalidate with the origin before treating it as fresh—unlike no-store, which forbids keeping it.
Full Explanation
Cache-Control no-cache allows storage but requires revalidation with the origin before reuse as a fresh response. That enables a cheap validator hop instead of blind use of possibly stale bytes. It is distinct from no-store, which forbids retaining the representation.