Can you clarify what platforms you're discussing this on, so that things like "temporary cache" can be clear?

no-store responses still get stored in the Blink MemoryCache, AIUI, which is bounded by the renderer lifetime, which is tangentially quasi-bounded by the "Fetch group" lifetime notion in the fetch spec.

If we do decide to drop, that's something that should be coordinated with the Fetch spec.

Per title, this is about "no state prefetch", which is the replacement for prerendering.  The current implementation of this downloads the main frame document to a renderer, discovers subresources (Not sure if we just run the preload scanner or do something more), and then downloads them all to the browser's cache, never passing the bodies to the renderer.

rsleevi: this is for NoStatePrefetch which is a "simpler" version of pre-rendering. The renderer loads only the main request, runs the preload scanner on it and issues a bunch of "prefetch" requests for sub resources. These requests are only used to warm up the HTTP cache, the renderer does not even get the responses back (and thus does not put them in its own cache).

For this to work well, it seems interesting to support no-store resources as well.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Seems like any work here would take significant investment, and I don't think the network team is interested in that.