You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jonathan Moore (JIRA)" <ji...@apache.org> on 2010/09/08 21:37:33 UTC
[jira] Updated: (HTTPCLIENT-992) cache should not generate stale
responses to requests explicitly requesting first-hand or fresh ones
[ https://issues.apache.org/jira/browse/HTTPCLIENT-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Moore updated HTTPCLIENT-992:
--------------------------------------
Attachment: stale-responses-to-explicit-requests.patch
The attached patch addresses this issue by either propagating the IOException (for no-cache requests) or by generating a 504 (Gateway Timeout) error.
This patch is contributed to the ASF with the permission of my employer.
> 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-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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org