A Cisco API response includes Expires and Age headers alongside usable Cache-Control. How should a consumer use Expires and Age?
Select an answer to reveal the explanation.
Short Explanation
Expires is the “best by” date; Age is how long the carton has already sat on the shelf. They help you skip a needless trip—but they never trump an explicit no-store, and Cache-Control still leads when both speak.
Full Explanation
Expires provides an absolute freshness end; Age indicates how long a stored response has already lived. Together they help consumers avoid redundant GETs. Prefer Cache-Control when present, and never let Expires or Age override an explicit no-store. These are standard HTTP freshness hints, not vendor cache products.