[
https://issues.apache.org/jira/browse/HTTPCLIENT-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699280#comment-13699280
]
Francois-Xavier Bonnet commented on HTTPCLIENT-1361:
----------------------------------------------------
I just committed a fix for both:
HTTPCLIENT-1361: stale-while-revalidate should work also without last-modified
nor etag
HTTPCLIENT-1368: stale-if-error request cache directive should also apply to
non-revalidatable cache entries
I added some unit tests but it was not easy to figure out the impact.
Could someone review?
> stale-while-revalidate should work also without last-modified nor etag
> ----------------------------------------------------------------------
>
> Key: HTTPCLIENT-1361
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1361
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 4.3 Beta1
> Reporter: Francois-Xavier Bonnet
> Priority: Minor
> Fix For: 4.3 Beta3
>
>
> Currently stale-while-revalidate mechanism works only if the cache entry
> contains a last-modified or a etag header. It should work also for cache
> entries with expires or max-age.
> The specification is not very clear about what a revalidation is, but in the
> example there is no last-modified nor etag, only a cache-control: max-age
> http://tools.ietf.org/html/rfc5861
> If everybody agrees, I can work on a fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
