cache module should handle out-of-order validations properly and 
unconditionally refresh
----------------------------------------------------------------------------------------

                 Key: HTTPCLIENT-997
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-997
             Project: HttpComponents HttpClient
          Issue Type: Improvement
          Components: Cache
    Affects Versions: 4.1 Alpha2
            Reporter: Jonathan Moore


There is a protocol recommendation that when we attempt to revalidate a cache 
entry, but we receive a response that has a Date header that's actually *older* 
than that of our current entry, we SHOULD revalidate again unconditionally with 
either max-age=0 or no-cache (since some upstream cache would appear to be 
out-of-date).

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.6



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

Reply via email to