[
https://issues.apache.org/jira/browse/CB-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666449#comment-13666449
]
Kevin Matassa commented on CB-3071:
-----------------------------------
Along with an example of headers, I've included 2 snapshots of the apache
access logfile. One snapshot shows GET requests being serviced (200) after the
cold start, while the other shows the server returning (304) indicating the
client cache is good. If the client app is restarted while the cache has still
got good artifacts, (200)s will again re-appear as the client refills its
cache after the startup.
> 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
> Attachments: apache server 200 on GET requests from IOS Cordova
> client.pdf, apache server 304 on GET requests from cordova client.pdf,
> headers
>
>
> 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
