Return-Path: X-Original-To: apmail-cordova-issues-archive@minotaur.apache.org Delivered-To: apmail-cordova-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4920104CF for ; Tue, 23 Apr 2013 18:45:17 +0000 (UTC) Received: (qmail 46783 invoked by uid 500); 23 Apr 2013 18:45:17 -0000 Delivered-To: apmail-cordova-issues-archive@cordova.apache.org Received: (qmail 46762 invoked by uid 500); 23 Apr 2013 18:45:17 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 46746 invoked by uid 99); 23 Apr 2013 18:45:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Apr 2013 18:45:17 +0000 Date: Tue, 23 Apr 2013 18:45:17 +0000 (UTC) From: "Shazron Abdullah (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CB-3071) App cache is invalidated after complete restart of an app 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/CB-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-3071: --------------------------------- Fix Version/s: 2.8.0 Not sure what's going on here. Slated for 2.8.0 > App cache is invalidated after complete restart of an app > --------------------------------------------------------- > > Key: CB-3071 > URL: https://issues.apache.org/jira/browse/CB-3071 > Project: Apache Cordova > Issue Type: Bug > Components: iOS > Affects Versions: 2.5.0 > Reporter: Shazron Abdullah > Assignee: Shazron Abdullah > Fix For: 2.8.0 > > > I have this report from a developer: > We've recently upgraded from 2.2 to 2.5 on IOS. > In 2.2, our application leveraged cached assets after a complete restart of the application. In 2.5 the same scenario always requests new assets from the web server. The web server has not changed, and it returns caching instructions with the content. Once the application is running, the cached assets are utilized as we expect. > Is this by design? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira