Rest API - Request and Response Format
Why might a server choose to use both
Cache-Control: max-age=0, must-revalidate and an ETag header together?Why might a server choose to use both Cache-Control: max-age=0, must-revalidate and an ETag header together?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze max-age=0 and must-revalidate
This combination means cached content is stale immediately and must be revalidated before use.Step 2: Understand ETag role
ETag provides a way to check if the cached content matches the server's current version.Step 3: Combine effects
Together, they allow caching but require clients to confirm content freshness, saving bandwidth if unchanged.Final Answer:
To allow clients to cache content but verify freshness before use -> Option BQuick Check:
max-age=0 + must-revalidate + ETag = cache with freshness check [OK]
Quick Trick: Use max-age=0 + must-revalidate + ETag for cache validation [OK]
Common Mistakes:
- Thinking this disables caching completely
- Confusing with content type headers
- Assuming clients ignore must-revalidate
Master "Request and Response Format" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes