You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Adam Patacchiola (JIRA)" <ji...@apache.org> on 2014/01/13 19:44:51 UTC

[jira] [Comment Edited] (HTTPCLIENT-1347) gzip responses doubly cached

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

Adam Patacchiola edited comment on HTTPCLIENT-1347 at 1/13/14 6:42 PM:
-----------------------------------------------------------------------

It looks like express has changed since the time of submission to default to not compressing binary files. I will upload new server code that sends back gzipped responses which causes the issue in the client.



was (Author: madman6000):
It looks like express has changed since the time of writing to default to not compressing binary files. I will upload new server code that sends back gzipped responses which causes the issue in the client.


> 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, 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org