New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 663969 link

Starred by 1 user
Status: WontFix
Owner:
█ allada@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Cc:
█ hdodda@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

For few users , new version of javascript file is not loading

Reported by vaibhav8...@gmail.com, Nov 10 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36

Steps to reproduce the problem:
1. Open www.sce.com
2. Open Network tab
3. There is file RA:collection with our changes.

What is the expected behavior?
It should pick the latest changes done in October and November without clearing the cache or pressing F5.

What went wrong?
Browser is picking the old javascript file .
User need to clear cache or press F5. There are more than 6 million users.

Did this work before? N/A 

Chrome version: 54.0.2840.87  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
TopLoginIssue.docx
1.3 MB Download

Comment 1 by hdodda@chromium.org, Nov 11 2016

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on windows 10 using chrome stable M54 #54.0.2840.98.

Attached screenshot for reference.

Could you please check with chrome latest stable and if you still face the issue , please write us with your observations.

Thanks !
663969.png
2.9 MB View Download

Comment 2 by durga.behera@chromium.org, Nov 14 2016

Components: -Blink Platform>DevTools>Network
vaibhav8921@ : Could you please update the thread according to the above comment # 1.

Comment 3 by l...@chromium.org, Nov 14 2016

Owner: allada@chromium.org

Comment 4 by allada@chromium.org, Nov 15 2016

Status: WontFix (was: Unconfirmed)
This is within the HTTP cache spec. This site is not providing headers that are telling it not to use cache, so chrome is using in memory cache.

The only indication I see that says not to use cache is:

"Expires:Tue, 15 Nov 2016 06:20:11 GMT" However, the server time for this request is:
"Date:Tue, 15 Nov 2016 01:06:30 GMT"

If you instruct chrome via headers to not use cache it should work properly.
►

Sign in to add a comment