[HTTPCLIENT-992] cache should not generate stale responses to requests explicitly requesting first-hand or fresh ones

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.1 Alpha2
• Fix Version/s: 4.1 Beta1
• Component/s: HttpCache
• Assignee: Unassigned
• Reporter: Jonathan Moore
• Created: 08/Sep/10 19:34
• Updated: 25/Jan/11 11:00
• Resolved: 08/Sep/10 20:45

Description

The current implementation will serve a stale response in the case that it has a stale cache entry but revalidation with the origin fails. However, the RFC says we SHOULD NOT do this if the client explicitly requested a first-hand or fresh response (via no-cache, max-age, max-stale, or min-fresh).