[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arturo Bernal updated HTTPCLIENT-1347: -- Attachment: output.out > 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: Stuck > > 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 ( < 100 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arturo Bernal updated HTTPCLIENT-1347: -- Attachment: (was: output.out) > 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: Stuck > > 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 ( < 100 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arturo Bernal updated HTTPCLIENT-1347: -- Attachment: output.out > 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: Stuck > > 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 ( < 100 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arturo Bernal updated HTTPCLIENT-1347: -- Attachment: Archive.zip > 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: Stuck > > 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 ( < 100 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Labels: stuck volunteers-wanted (was: ) Fix Version/s: (was: 5.0) Stuck > 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 > Labels: stuck, volunteers-wanted > Fix For: Stuck > > Attachments: httpClientCacheTest.tar.gz, httpClientTestServer.js, > 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 > > > 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 ( < 100 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.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Fix Version/s: (was: 4.4 Final) 5.0 > 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 > Fix For: 5.0 > > 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 ( < 100 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.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1347: -- Issue Type: Improvement (was: Bug) I'm reclassifying this as an improvement, rather than as a bug, because there isn't a protocol violation here, and I do think there is a workaround within the existing API to build the type of cache storage you are looking for without doubly storing response bodies. > 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 > 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Campbell updated HTTPCLIENT-1347: - Attachment: Showing_entry_pointer.png > 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Campbell updated HTTPCLIENT-1347: - Attachment: Screen Shot 2014-01-13 at 3.56.19 PM.png This is not unexpected - one is a key to the vary (variant) which in this case is the GZIPed version. > 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, 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Patacchiola updated HTTPCLIENT-1347: - Attachment: httpClientTestServer.js new server code that always returns gzipped responses. > 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Campbell updated HTTPCLIENT-1347: - Attachment: Screen Shot 2014-01-11 at 7.11.36 PM.png > 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 > > > 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Fix Version/s: (was: 4.3.2) 4.4 Final Anyone with HTTP caching expertise might be willing to look into this one? Oleg > 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: httpClientCacheTest.tar.gz > > > 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 ( < 100 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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Fix Version/s: (was: 4.3 Final) 4.3.1 > 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.3.1 > > Attachments: httpClientCacheTest.tar.gz > > > 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 ( < 100 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Fix Version/s: (was: 4.3 Beta2) 4.3 Final > gzip responses doubly cached > > > Key: HTTPCLIENT-1347 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: Cache >Affects Versions: 4.2.5 > Environment: ARCH Linux kernel 3.8.8-1 > node.js 0.8.22 >Reporter: Adam Patacchiola > Fix For: 4.3 Final > > Attachments: httpClientCacheTest.tar.gz > > > 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 ( < 100 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski updated HTTPCLIENT-1347: -- Fix Version/s: 4.3 Beta2 Than it will have to wait until 4.3b2. Oleg > gzip responses doubly cached > > > Key: HTTPCLIENT-1347 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: Cache >Affects Versions: 4.2.5 > Environment: ARCH Linux kernel 3.8.8-1 > node.js 0.8.22 >Reporter: Adam Patacchiola > Fix For: 4.3 Beta2 > > Attachments: httpClientCacheTest.tar.gz > > > 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 ( < 100 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Patacchiola updated HTTPCLIENT-1347: - Attachment: httpClientCacheTest.tar.gz tests > gzip responses doubly cached > > > Key: HTTPCLIENT-1347 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: Cache >Affects Versions: 4.2.5 > Environment: ARCH Linux kernel 3.8.8-1 > node.js 0.8.22 >Reporter: Adam Patacchiola > Attachments: httpClientCacheTest.tar.gz > > > Compressed responses are cached twice. > Run the attached server and client tests. Create an "asset"s directory under > where you are running the server and add two files named 1 and 2 ( < 100 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Patacchiola updated HTTPCLIENT-1347: - Description: 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 ( < 100 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. was: Compressed responses are cached twice. Run the attached server and client tests. Create an "asset"s directory under where you are running the server and add two files named 1 and 2 ( < 100 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. > gzip responses doubly cached > > > Key: HTTPCLIENT-1347 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1347 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: Cache >Affects Versions: 4.2.5 > Environment: ARCH Linux kernel 3.8.8-1 > node.js 0.8.22 >Reporter: Adam Patacchiola > Attachments: httpClientCacheTest.tar.gz > > > 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 ( < 100 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
