News for hackers. Stuff that matters.
Re:Using Immutable Caching to Speed Up the Web by niftich on Thursday January 26, 2017 @02:47PM (#13494640)
They could just be seeing 10%-20% of the people doing a Ctrl+F5 'force refresh' -- after all, they're speculating, and have no real data on whether browser or user behavior is responsible for the numbers they're seeing.
Re:Using Immutable Caching to Speed Up the Web by Tenoke on Thursday January 26, 2017 @04:08PM (#13495257)
You think they didn't test their assumption?
Re:Using Immutable Caching to Speed Up the Web by niftich on Thursday January 26, 2017 @05:06PM (#13495684)
I think they did, but there's not enough information available to reliably distinguish 'normal' reloads from 'force-reloads', unless they ran onKeyDown javascript and correlated the events after the fact.

A comment from Facebook [1] on the Chrome bug says they started logging 'window.performance.navigation.type', which distinguishes between [2] normal navigation, reload, history traversal (back/forward), and undefined.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=505048... [2] https://developer.mozilla.org/en-US/docs/Web/API/Navigation_...

Re:Using Immutable Caching to Speed Up the Web by tyingq on Thursday January 26, 2017 @04:51PM (#13495566)
Firefox themselves appear to have tested and confirmed that regular F5/Refresh (not Ctrl+F5) causes revalidation: http://bitsup.blogspot.de/2016/05/cache-control-immutable.ht...