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 2010/07/30 14:38:16 UTC
[jira] Resolved: (HTTPCLIENT-967) allow cache to be configured as a
non-shared (private) cache
[ https://issues.apache.org/jira/browse/HTTPCLIENT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-967.
------------------------------------------
Resolution: Fixed
Patch checked in.
Oleg
> allow cache to be configured as a non-shared (private) cache
> ------------------------------------------------------------
>
> Key: HTTPCLIENT-967
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-967
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Fix For: 4.1 Alpha3
>
> Attachments: nonshared-cache-2.patch, nonshared-cache-3.patch, nonshared-cache.patch
>
>
> Currently the CachingHttpClient only behaves as a shared cache, which is a safe and conservative assumption. However, in some settings, it would be appropriate to be able to configure the CachingHttpClient as a non-shared cache, which would make more responses cacheable, including:
> * responses to requests with Authorization headers
> * responses with 'Cache-Control: private'
> * ability to serve stale responses when invalidation fails for 'Cache-Control: proxy-revalidate'
--
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