[
https://issues.apache.org/jira/browse/HTTPCLIENT-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907404#action_12907404
]
Jonathan Moore commented on HTTPCLIENT-992:
-------------------------------------------
Answered my own question by reading the RFC:
"max-age
Indicates that the client is willing to accept a response whose age is no
greater than the specified time in seconds. Unless max- stale directive is also
included, the client is not willing to accept a stale response."
So option (b) is actually the correct behavior here.
> cache should not generate stale responses to requests explicitly requesting
> first-hand or fresh ones
> ----------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-992
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-992
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: stale-response-to-explicit-request-optionB.patch,
> stale-responses-to-explicit-requests.patch
>
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
