Open Bug 1411973 Opened 7 years ago Updated 2 years ago

Cache does not update when Developer Tools are open

Categories

(DevTools :: Netmonitor, defect, P4)

57 Branch
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: fabian.letsch, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171023180840 Steps to reproduce: Host a site with browser cache enabled assets. (css) Open Developer Tools and check the checkbox for disabling cache when developer tools are open Change css and html on the website in your backend of that site while keeping developertools open, so that you see changes on the site, browser caching should still be enabled on your website (but not in developer tools). Close tab Open site with developer tools turned off Actual results: The old (cached) site was loaded Expected results: The new site with the new changes should have loaded
Component: Untriaged → Developer Tools
Component: Developer Tools → Developer Tools: Netmonitor
@Fabian: I can't see the issue on my machine. Can you please attach your (simple) test page and precise steps what to change to see the problem? Honza
Flags: needinfo?(fabian.letsch)
Priority: -- → P4
Sorry for my late reaction. I will do my best to create such a testpage. This issues is work related but im not sure if i can use my work environment, so i will have to set something up myself. This is hard for me, im usually only a frontend guy and i dont configure servers and http or caching.
I think it would be a better idea to replicate the problem locally and not on my server. For this purpose i have created a little nodejs script. I hope you know how to handle nodejs. otherwise we could agree to communicate somewhere else, maybe with a phonecall and i explain the problem and how to test this. https://pastebin.com/eDkgc1hy Step 1: install any newer version of nodejs: https://nodejs.org/en/ Step 2: create a file called "server.js" and paste the code of the pastebin into it. Step 3: Run that file via "node server.js" Step 4: Find out your local ip address, it should be something like 192.168.xxx.xxx where x are placeholders. On linux you can use ifconfig to find the local ip-address, i dont know how to figure that out on different systems. Step 5: open Firefox and connect to the node server by typing [yourip]:8081/ for me this was 192.168.2.105:8081 Step 6: Open developer Tools Step 7: Set checkbox in developer tools options, which activates that you keep the cache while devtools is open. Step 8: Go to http://[yourip]:8081/?changefile=1 a bunch of times (for me this was http://192.168.2.105:8081/?changefile=1) Step 9: go to [yourip]:8081/ - this should have the latest random number you have generated, it doesnt matter how often you open it. Step 10: close developer tools and go to [yourip]:8081/ - This now should have the random number from the first time you have opened up the website. I really hope you understand the problem and you know nodejs, otherwise we will have to figure this out differently.
Flags: needinfo?(fabian.letsch)
Dont use the reload Button to test this, but type the new ip into the addressbar, otherwise the problem sometimes doesnt occur.
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.