New issue
Advanced search Search tips

Issue 701323 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome caching issues

Reported by i...@money4yourmotors.com, Mar 14 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Apply a CSS change on a webpage
2. Change will not appear
3. Change will only appear with a F5 hard refresh

What is the expected behavior?
Webpages should refresh the cache without a hard refresh within Chrome.

What went wrong?
We updated our webpage and users could not see change due to this caching issue.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 10.0
Flash Version:
 

Comment 1 by mmenke@chromium.org, Mar 14 2017

Components: Internals>Network>Cache Blink>Loader
Could you please provide a net-internals log of this happening, and tell us which resource is the one you expect not to be cached?  Instructions:  https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

It's most likely Chrome is behaving correctly.  Unless you have headers indicating a resource shouldn't be cached at all, Chrome will reuse resource on soft-reloads.  End users often use reload when a page is failing to load due to network issues, and the current soft-reload behavior is targeted at that use case.

Comment 2 by mmenke@chromium.org, Mar 14 2017

Labels: Needs-Feedback

Comment 3 by mmenke@chromium.org, Mar 14 2017

Also, could be clarify:  Is the CSS in question being re-used (When you don't want it to be) just on soft reloads, or also on new navigations?
I guess issue 612701?
Labels: Needs-Milestone

Comment 7 by rch@chromium.org, Mar 23 2017

Just a reminder that we're hoping for more information from you as mentioned in c#1.  Could you upload a network internals dump (see https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details ) taken while reproducing this problem?  Without that information we'll be unable to make progress on this and need to close the bug.

Comment 8 by mmenke@chromium.org, Apr 20 2017

Status: Archived (was: Unconfirmed)
Closing due to lack of followup.  Feel free to file a new bug if you still have the issue, with the requested log.

Sign in to add a comment