[
https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682369#comment-13682369
]
Jon Moore commented on HTTPCLIENT-1370:
---------------------------------------
Ah, I see. You're pointing out that the response is being placed into the
cache, and I'm pointing out that those cache entries will never be consulted or
served up to a caller.
To summarize, there's no non-compliant behavior going on here, although there's
some waste in the implementation (because it doesn't make sense to use up cache
space on something that will never be served to a client).
There's a simpler fix, though, which is to do the modification in CachingExec /
CachingHttpClient to prevent non-request-cacheable executions from being stored
in the cache as well. I think that more broadly covers the situation.
> Response to Non-GET Requests Should Never be Cached With the Default Response
> CachingPolicy
> -------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1370
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1370
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: CacheHttpClient Caching components
> Affects Versions: 4.3 Beta2
> Reporter: James Leigh
> Labels: patch
> Fix For: 4.3 Beta3
>
> Attachments: HTTPCLIENT-1370.patch
>
>
> HttpClient caches response to non-GET requests when a shared cache is used
> and an Authorization header is present with Cache-Control: public.
--
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]
