You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jonathan Moore (JIRA)" <ji...@apache.org> on 2010/09/13 18:18:33 UTC
[jira] Updated: (HTTPCLIENT-995) cache returns cached responses
even if validators not consistent with all conditional headers
[ https://issues.apache.org/jira/browse/HTTPCLIENT-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Moore updated HTTPCLIENT-995:
--------------------------------------
Attachment: mismatched-conditionals.patch
The attached patch addresses this issue. In addition, we are now very explicit about not using cached responses for conditionals we don't currently understand/support, namely: If-Range, If-Match (for GETs), and If-Unmodified-Since (for GETs).
This patch is contributed to the ASF with the permission of my employer.
> cache returns cached responses even if validators not consistent with all conditional headers
> ---------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-995
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-995
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: mismatched-conditionals.patch
>
>
> This is a MUST-level requirement in the RFC, where if both ETags and Last-Modified dates are used as validators in a conditional request, a cache cannot return a cached response unless it is consistent with all the conditional headers in the request. There is a unit test for this already, but it is incorrect (it uses 'If-Unmodified-Since' instead of 'If-Modified-Since' in the test case).
--
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