[
https://issues.apache.org/jira/browse/HTTPCLIENT-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Moore updated HTTPCLIENT-961:
--------------------------------------
Attachment: invalidating-requests.patch
The attached patch addresses this issue by also invalidating absolute and
relative URIs in Content-Location headers and absolute URIs in Location
headers, as long as they address the same host as the original request.
Includes updates to associated unit tests.
This patch is contributed to the ASF with the permission of my employer.
> not all applicable URIs are invalidated on PUT/POST/DELETEs that pass through
> client cache
> ------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-961
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-961
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: invalidating-requests.patch
>
>
> "Some HTTP methods MUST cause a cache to invalidate an entity. This is either
> the entity referred to by the Request-URI, or by the Location or
> Content-Location headers (if present). These methods are: PUT, DELETE, POST."
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.10
> The current caching implementation only invalidates the Request URI, and not
> those present in the Location or Content-Location headers on the request.
> I have a patch that fixes this which I will upload momentarily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
