[
https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682322#comment-13682322
]
Jon Moore commented on HTTPCLIENT-1370:
---------------------------------------
Hi James,
This particular case is governed by:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.2
"9.2 OPTIONS. ... Responses to this method are not cacheable."
This is already captured in the CacheableRequestPolicy. The end-to-end test is
covered by TestProtocolRequirements#testResponsesToOPTIONSAreNotCacheable.
In other words, for your test case, the thing that makes the response not
cacheable is a property of the *request* (its method) and not a property of the
*response*.
Jon
> 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]