[
https://issues.apache.org/jira/browse/HTTPCLIENT-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252339#comment-13252339
]
Jon Moore commented on HTTPCLIENT-1183:
---------------------------------------
Actually, an incoming HTTP/1.0 request gets upgraded to HTTP/1.1 by
RequestProtocolCompliance, and hence is suitable for being satisfied by the
cache. The check in here is to guard against non-HTTP/1.x requests being
satisfied by the cache--since it doesn't understand those protocols it is not
safe for the cache to cache responses.
Can you produce a unit test that shows that an HTTP/1.0 request that receives a
cacheable response doesn't get served from cache?
> HTTP/1.0 requests not serveable from cache
> ------------------------------------------
>
> Key: HTTPCLIENT-1183
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1183
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Cache
> Reporter: Francois-Xavier Bonnet
>
> Any HTTP/1.0 request is considered as not serveable from cache (only HTTP/1.1
> requests are serveable from cache). This is implemented in method
> org.apache.http.impl.client.cache.CacheableRequestPolicy.isServableFromCache(HttpRequest)
> What is the reason for this behaviour? According to the specifications,
> HTTP/1.0 request are supposed to be cacheable even if the mechanism is more
> primitive than for HTTP/1.1 requests (only based on Expires and Last-Modified
> headers).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
