You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2013/06/05 16:56:20 UTC
[jira] [Updated] (HTTPCLIENT-1361) stale-while-revalidate should
work also without last-modified nor etag
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPCLIENT-1361:
------------------------------------------
Fix Version/s: 4.3 Beta3
> 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: Cache
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org