After a successful PUT to a Cisco resource, a follow-up GET returns 200 with a different ETag than the client had cached. What should happen to the old stored body?
Select an answer to reveal the explanation.
Short Explanation
A new coat-check number means the old stub is retired. When the ETag changes after a write or a fresh 200, drop or replace the old body—clinging to it is a stale-read bug, not an optimization.
Full Explanation
A new ETag signals that the prior stored representation is no longer current. Consumers must invalidate or replace that cache entry. Continuing to serve or validate against the old body after a successful write or a 200 with a new validator produces stale reads.