[
https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790655#comment-17790655
]
ASF subversion and git services commented on HTTPCLIENT-1347:
-------------------------------------------------------------
Commit fb2411815b8c57fb100f67b427afefe90edcf633 in httpcomponents-client's
branch refs/heads/5.3.x from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=fb2411815 ]
HTTPCLIENT-2277, HTTPCLIENT-1347: Revision of the variant handling by the HTTP
cache implementations
* Cache entries now can be of two distinct types: root entries containing a map
of known representation variants of the same resource and resource entries
containing a resource potentially sharable by multiple resource entries. The
same entry cannot have a variant map and a resource at the same time
* Cache entry factory class added to the public APIs
> gzip responses doubly cached
> ----------------------------
>
> Key: HTTPCLIENT-1347
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpCache
> Affects Versions: 4.2.5
> Environment: ARCH Linux kernel 3.8.8-1
> node.js 0.8.22
> Reporter: Adam Patacchiola
> Priority: Major
> Labels: stuck, volunteers-wanted
> Fix For: 5.4-alpha1
>
> Attachments: Archive.zip, 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, output.out
>
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
