U4-5312 - Need to ensure the cache headers are set correctly for templates, Chrome will keep the cached value by default now.

Created by Shannon Deminick 05 Aug 2014, 15:33:35 Updated by Shannon Deminick 07 Aug 2014, 17:15:25

Relates to: U4-2462

sometimes when you are editing in Chrome and you save your templates and then move away from the template editor and return it would show the template as it was prior to the edit. However on disk the file was as expected. What we found is that Chrome has is the feature labeled "Predict network actions to improve page load performance" if it is set then you will get unpredictable results, as chrome will sometimes give you old versions of the page. Make sure its off.

Comments

Shannon Deminick 05 Aug 2014, 16:43:45

Some more info:

https://developers.google.com/chrome/whitepapers/prerender

http://www.stevesouders.com/blog/2014/04/30/unexpected-prerender-in-chrome/

chrome://predictors/

chrome://net-internals/#prerender


Shannon Deminick 05 Aug 2014, 16:56:50

I've ensured that all client cache is disabled for both mvc views and master page editing, just not sure what else this affects. I also cannot replicate this locally so am unsure if this fix actually solves the issue.

rev: 62d3dc78fa21e7438531eb7134692d70ff59c5fb


Peter Gregory 05 Aug 2014, 23:20:37

We only really saw this issue occurring in the template editor with MVC views (we weren't using MasterPages).


Shannon Deminick 07 Aug 2014, 17:15:23

Well I can't see any sort of caching happening with a no-cache header since we're not explicitly telling browsers to definitely not cache these requests so even if Chrome tries to smartly determine what you will do in the future, it should never be returned from cache now. Will close this issue.


Priority: Normal

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version: 7.1.5, 6.2.2

Sprint:

Story Points:

Cycle: