Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C20E31007B for ; Mon, 12 Jan 2015 09:52:33 +0000 (UTC) Received: (qmail 69365 invoked by uid 500); 12 Jan 2015 09:52:35 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 69313 invoked by uid 500); 12 Jan 2015 09:52:35 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 69301 invoked by uid 99); 12 Jan 2015 09:52:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jan 2015 09:52:35 +0000 Date: Mon, 12 Jan 2015 09:52:35 +0000 (UTC) From: "Oleg Kalnichevski (JIRA)" To: dev@hc.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HTTPCLIENT-1579) CacheValidityPolicy does not correctly handle 304 Not Modified freshness MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HTTPCLIENT-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Kalnichevski resolved HTTPCLIENT-1579. ------------------------------------------- Resolution: Cannot Reproduce > CacheValidityPolicy does not correctly handle 304 Not Modified freshness > ------------------------------------------------------------------------ > > Key: HTTPCLIENT-1579 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1579 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: HttpClient > Affects Versions: 4.3.3, 4.3.4, 4.3.5, 4.3.6 > Reporter: Nitin Kumar > > When a cached response expires, http cache client correctly makes a new request to the http server. When the response is still fresh at the server side, the server responds with HTTP/1.1 304 Not Modified and sends in a new Expires: header. > On subsequent request, when the cache entry should be still valid as per the time stamp received in the Expires header from the last call, CacheValidityPolicy tries to validate the cache entry in the isResponseFresh() method and incorrectly marks the the entry as stale. > The result is that http cache client keeps making new requests to the http server. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org