[
https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723732#comment-17723732
]
Arturo Bernal commented on HTTPCLIENT-1347:
-------------------------------------------
I am writing to provide an update on the testing conducted for Apache
HttpComponents 5.3. I have run multiple tests to verify the functionality of
the new version and can confirm that it is operating as expected.
The test involved setting up a local HTTP server using the HttpComponents and
serving static files from a specified directory. The server correctly processed
GET requests and served the requested files with appropriate cache-control
headers, thus enabling client-side caching.
Repeated requests for the same file were served from the cache when valid,
which is a clear indication that the caching mechanism is working as expected.
The server also correctly processed different paths and served the
corresponding files.
Here is a summary of the test results:
# GET request to {{{}http://localhost:8000/assert/1{}}}: Successful. Response
served with cache-control headers.
# GET request to {{{}http://localhost:8000/assert/2{}}}: Successful. Response
served with cache-control headers.
# Subsequent GET requests to the above URLs were served from the cache, as
intended.
you can see the detail here [^output.out]
Based on these test results, I believe that Apache HttpComponents 5.3 is
functioning correctly and is ready for further use or deployment.
In order to facilitate replication of these tests, I have attached a .zip file
containing the necessary classes to set up and run the local server in the
Apache HttpComponents environment. You can use these classes to perform the
same tests that I did.
Please let me know if you require additional information or further testing.
> 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 ( < 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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
