[
https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869994#comment-13869994
]
Joe Campbell commented on HTTPCLIENT-1347:
------------------------------------------
Ok - So the first screen shot shows the entries, they look like they are
duplicated, in fact they are not. These items comprise a 'root' entry and a
series of Variant pointers to the entries that contain a variant based on what
was asked for. In this case, we asked for a gzip variant, which has the effect
of placing a root entry and a variant entry into the hash. The second screen
shot I put up there shows the HASH entry links using red arrows.
I believe that the item in Purple is a 'copy' of the response (as you point
out) because we request GZIP and got it that was stored at the root entry as
well as the variant as currently this is the only thing that the cache knows
about. I believe this to also be correct caching behavior when dealing with
the spec and variant caching.
> gzip responses doubly cached
> ----------------------------
>
> Key: HTTPCLIENT-1347
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpCache
> Affects Versions: 4.2.5
> Environment: ARCH Linux kernel 3.8.8-1
> node.js 0.8.22
> Reporter: Adam Patacchiola
> Fix For: 4.4 Final
>
> Attachments: Screen Shot 2014-01-11 at 7.11.36 PM.png, Screen Shot
> 2014-01-13 at 3.56.19 PM.png, Showing_entry_pointer.png,
> httpClientCacheTest.tar.gz, httpClientTestServer.js
>
>
> Compressed responses are cached twice.
> Run the attached server (node.js 0.8.22) and client tests. Create an "assets"
> directory under where you are running the server and add two files named 1
> and 2 ( < 1000000 bytes) . You will see that after the test is run the cache
> dump output displays 2 sets of entries for each request, each containing the
> full content length of the file.
> Changing the implementation of HttpCacheStorage updateEntry to not update non
> existent entries (as I believe the correct implementation should do) throws
> exceptions.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
