UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Example URL:

Steps to reproduce the problem:
In order to be able to reproduce this you need to control a web server, so please be prepared to read the description carefully and to do some work.

1. visit a website that loads some static file such as javascript or css.
Let's say you visit https://site.com/index and that this page loads https://site.com/somescript.js
2. somescript.js gets cached as expected
3. reload the page. somescript.js gets loaded from cache as expected
4. modify somescript.js on the server
5. reload the index page: somescript.js is still loaded from cache and hence is outdated: this is expected.
6. Now explicitly load https://site.com/somescript.js on a separate tab, by typing the address manually. The outdated version is still loaded from cache and this is still expected
7. In this tab where you have loaded somescript.js separately, hit Ctrl+F5. This forces a reload from the server, so finally you get the up-to-date version, as expected
8. Go back to the tab where you had https://site.com/index open, and reloaded (NOT Ctrl+reload, just a regular reload)

What is the expected behavior?
Since, at step 6-7, we have succesfully loaded the up-to-date version of somescript.js, this should have been saved to cache overwriting the outdated one, so, even if somescript.js is served from cache at step 8, the updated version should be loaded

What went wrong?
at step 8, somescript.js is loaded from cache, and it is STILL the outdated version that we have seen in steps 1-6, despite the fact we have already obtained a more updated version through forced reloading at step 7.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 
Flash Version: