Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SW Audit: Verify that new index.html content will be fetched and served #2147

Open
samccone opened this issue May 4, 2017 · 1 comment
Open

SW Audit: Verify that new index.html content will be fetched and served #2147

samccone opened this issue May 4, 2017 · 1 comment
Labels
feature P3

Comments

@samccone
Copy link
Contributor

samccone commented May 4, 2017

@paulirish and I ran into this on caltrainschedule.io

While we thought our SW was operating correctly, it was always satisfied by the assets in the cache. As a result, it never went looking for a new asset from the network and the user only saw stale stuff.

The downsides of cache-first serving policy, I guess. 🐐

(issue authored by paul. thanks sam)
@paulirish
Copy link
Member

Simulating this via the protocol will be a pretty big challenge. I'm also not sure we can do it today.. might have to wait for protocol layer support for changing response bodies.

But it'll be powerful when it's available. :)
@paulirish paulirish changed the title SW Audit: Verify that new index.html content will be available after 2 refreshes Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature P3
3 participants
@paulirish @samccone @patrickhulce