[
https://issues.apache.org/jira/browse/HTTPCLIENT-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Moore updated HTTPCLIENT-994:
--------------------------------------
Attachment: max-stale-no-refactor.patch
I have attached another patch that addresses the issue without the major
refactoring of HttpCacheEntry. I did, however, go ahead and remove the
CacheEntry test class here, and several of the unit tests I touched while
fixing the bug are now no longer mock tests, which makes them a lot less
brittle.
This patch also fixes a bug in the processing of min-fresh (semantics were not
being applied correctly).
This patch is contributed to the ASF with the permission of my employer.
> cache does not allow client to override origin-specified freshness using
> max-stale
> ----------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-994
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-994
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: max-stale-no-refactor.patch, max-stale.patch
>
>
> According to the RFC, the default freshness lifetime is supposed to be the
> LEAST restrictive of that specified by the origin, the client, and the cache.
> Right now, a client can't use 'max-stale' to relax the freshness constraints
> to get a cache hit without validation occuring first.
--
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]
