[
https://issues.apache.org/jira/browse/HTTPCLIENT-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046559#comment-13046559
]
Jon Moore commented on HTTPCLIENT-1100:
---------------------------------------
By the way, I suppose this is presumed by my earlier response, but I agree this
is a bug. The cache entry should only be considered invalid if there is a
Content-Length header present and it does not match the length of the cached
response body. If a Content-Length header is not present, then the entry should
be presumed valid (at least per the sense of this test).
> Missing Content-Length header makes cached entry invalid
> --------------------------------------------------------
>
> Key: HTTPCLIENT-1100
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1100
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.1.1, 4.1.2, 4.2 Alpha1
> Reporter: Bart Robeyns
> Labels: cache, contentlength
> Attachments: MissingContentLength.patch
>
>
> A cached entry whose original response didn't carry a Content-Length header,
> should not be rejected for considered invalid because the length of its
> cached content is different from the non-existing Content-Length header
> value. The attached patch only verifies the lengths if the header was
> originally present.
--
This message is automatically generated by JIRA.
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]
