[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870007#comment-13870007
 ] 

Joe Campbell commented on HTTPCLIENT-1347:
------------------------------------------

If you look at the implementation of a BasicHttpCache - Your entry gets a 
'storeInCache' called... in this case the entry "hasVariants" which then calls 
storeVariantEntry();

This method then takes the entry and stores it AS a variant and produces a 
callback which would update the 'root' entry.  In this case, your method just 
stores the record that had just been stored as the variant version into the 
root version (non-variant). 

                @Override
                public void updateEntry(String arg0, HttpCacheUpdateCallback 
arg1)
                                throws IOException, HttpCacheUpdateException {

                        System.out.println("updating entry: " + arg0);
                        HttpCacheEntry entry = getEntry(arg0);
                        ----> putEntry(arg0, arg1.update(entry));
                }

> 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]

Reply via email to