resources loaded from cache even for hard reload (Ctrl+F5)
Categories
(DevTools :: Netmonitor, defect, P3)
Tracking
(Not tracked)
People
(Reporter: aryx, Unassigned)
References
(Blocks 1 open bug)
Details
What were you doing?
- Had https://senglehardt.com/test/trackingprotection/test_pages/social_tracking_protection.html open and the Network monitor open (cache not disabled).
- Pressed Ctrl+F5 (Windows 8.1) to reload the page.
What happened?
Except for the favicon.ico, all resources have a status 304 (Not Modified) - the former has the expected 200.
What should have happened?
All resources should have status code 200.
Anything else we should know?
Seeing this with 71.0a1, 70.0b1 and even builds from May (Gecko 68). But with the 69 profile (cloned from a shim), I don't see this behavior.
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:Honza, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 2•5 years ago
|
||
Thanks for the report Sebastian!
Unfortunately, I can't reproduce the report.
(Win10, Fx71)
Here is what I am doing
- Load https://senglehardt.com/test/trackingprotection/test_pages/social_tracking_protection.html
- Open DevTools select the Network panel. Make sure Cache is not disabled
- Reload the page - pressing F5
- All requests (except of the favicon.ico) are 304
- Reload the page - pressing Ctrl+F5
- All requests are 200
What am I doing wrong?
What could be different in our configs?
Honza
![]() |
Reporter | |
Comment 3•5 years ago
|
||
It depends where the focus is:
- Click into the content area.
- Press Ctrl+F5: Status code 200
- Click into the Network Monitor list area.
- Press Ctrl+F5: Status code 304 at least twice.
Updated•5 years ago
|
Comment 5•4 years ago
|
||
Experiencing this in Fedora Linux 5.9.11-100.fc32.x86_64 version 83.0
I try to reload a CSS file on http://localhost:8000 using CTRL+SHIFT+R or CTRL+F5 and the same cached version is shown. Opening the file in a private window bypasses the cache, so there is certainly an issue of the cache not being reloaded.
Updated•2 years ago
|
Description
•