You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2010/09/08 22:46:34 UTC

[jira] Resolved: (HTTPCLIENT-992) cache should not generate stale responses to requests explicitly requesting first-hand or fresh ones

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

Oleg Kalnichevski resolved HTTPCLIENT-992.
------------------------------------------

    Fix Version/s: 4.1 Alpha3
       Resolution: Fixed

Committed option B.

Oleg

> cache should not generate stale responses to requests explicitly requesting first-hand or fresh ones
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-992
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-992
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: Cache
>    Affects Versions: 4.1 Alpha2
>            Reporter: Jonathan Moore
>             Fix For: 4.1 Alpha3
>
>         Attachments: stale-response-to-explicit-request-optionB.patch, stale-responses-to-explicit-requests.patch
>
>
> The current implementation will serve a stale response in the case that it has a stale cache entry but revalidation with the origin fails. However, the RFC says we SHOULD NOT do this if the client explicitly requested a first-hand or fresh response (via no-cache, max-age, max-stale, or min-fresh).

-- 
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