New issue
Advanced search Search tips

Issue 849019 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

browser loading asset from cache while etag has changed on resource

Reported by cyprien....@gmail.com, Jun 2 2018

Issue description

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

Steps to reproduce the problem:
clone/download this repository
install server dependancies : npm i
install client dependancies : cd client && npm i
start server : cd .. && npm start
open a browser at http://localhost:5000/client/build/static/js/main.js
see Etag in headers
add some text to this component jsx : client/src/components/App/App.tsx
build the client : cd client && npm run build
switch to the browser, press f5, note that the file has been loaded via memory cache
press ctrl+f5 and see that the etag has changed, but the file was loaded from cache

What is the expected behavior?
file is not loaded from cache, but downloaded from the server, despite the Etag header has changed on the resource response

What went wrong?
The file is loaded from browser cache

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: 4.13.0-43
Flash Version:
 
Link to the test-case repository : https://github.com/Ctaque/vad-api

Comment 2 by b...@chromium.org, Jun 3 2018

Components: -Blink>Network Internals>Network>Cache
Labels: Needs-Milestone
Labels: Triaged-ET TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to building the client and running the build. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

Sign in to add a comment