Open Bug 1904797 Opened 8 months ago Updated 7 months ago

Network > Disable Cache still caches requests fetched from workers

Categories

(DevTools :: Netmonitor, defect, P2)

Firefox 127
defect

Tracking

(Not tracked)

People

(Reporter: tor, Unassigned)

References

(Blocks 2 open bugs)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0

Steps to reproduce:

Go to https://mupdf.com/wasm/demo/
Open the Network panel.
Click "Disable Cache".
Reload the page.

Actual results:

The mupdf-wasm.wasm resource was NOT reloaded. It was still fetched from cache, despite "Disable Cache" being checked.

Expected results:

mupdf-wasm.wasm should have been downloaded again.

The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Netmonitor
Product: Firefox → DevTools

jesup: Do you know if WASM files are using a different cache? The test case here is simply using fetch in order to load a wasm file but it always seems to be read from cache, regardless of our "disable cache" feature which sets Ci.nsIRequest.LOAD_BYPASS_CACHE as the defaultLoadFlags for the browsing context.

Worth noting that the request is issued from a worker, so maybe it's a general issue with fetch requests coming from workers?

Flags: needinfo?(rjesup)

It seems to be related to any fetch done in workers.

Here is a small test case (requiring a click to do a fetch from a worker):
http://techno-barje.fr/fission/worker-fetch/

Thanks Alex!

Let 's remove the need info for now. It sounds like workers don't really follow the load flags from the browsing context which loads them (which makes sense for shared/service workers, but a little less for web workers?)

Flags: needinfo?(rjesup)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Network > Disable Cache still caches WASM files. → Network > Disable Cache still caches requests fetched from workers
Severity: -- → S3
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.