hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Moore (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HTTPCLIENT-1035) cache should invalidate obsoleted entries mentioned in Content-Location
Date Sun, 26 Dec 2010 15:11:46 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jon Moore closed HTTPCLIENT-1035.


> cache should invalidate obsoleted entries mentioned in Content-Location
> -----------------------------------------------------------------------
>                 Key: HTTPCLIENT-1035
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1035
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: Cache
>    Affects Versions: 4.1 Beta1
>            Reporter: Jon Moore
>            Assignee: Jon Moore
>            Priority: Minor
>             Fix For: 4.1.0
>         Attachments: content-location-response-invalidation-test.patch
> From http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.6:
> If a cache receives a successful response whose Content-Location field matches that of
an existing cache entry for the same Request-URI, whose entity-tag differs from that of the
existing entry, and whose Date is more recent than that of the existing entry, the existing
entry SHOULD NOT be returned in response to future requests and SHOULD be deleted from the
> Current caching module doesn't do this (yet). As this is a recommendation (SHOULD) and
not a requirement (MUST) I am marking this as an improvement rather than a bug.

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

View raw message