Problem
nitroFetch(..., { cache: "no-store" }) adds Cache-Control: no-store on the standard request path, but the stream: true path currently ignores RequestInit.cache. On iOS, streaming requests use a disk-backed URLCache, so a caller can explicitly request no-store and still have the streamed response remain eligible for persistence.
This is especially important for authenticated responses containing tokens or other sensitive material.
Proposed fix
Reuse the existing cache-directive header mapping for both standard and streaming requests, with focused fetch-compliance coverage. This preserves the existing 32 MiB memory / 100 MiB disk cache for default requests; it does not disable caching globally.
I can send a small PR for this.
Problem
nitroFetch(..., { cache: "no-store" })addsCache-Control: no-storeon the standard request path, but thestream: truepath currently ignoresRequestInit.cache. On iOS, streaming requests use a disk-backedURLCache, so a caller can explicitly requestno-storeand still have the streamed response remain eligible for persistence.This is especially important for authenticated responses containing tokens or other sensitive material.
Proposed fix
Reuse the existing cache-directive header mapping for both standard and streaming requests, with focused fetch-compliance coverage. This preserves the existing 32 MiB memory / 100 MiB disk cache for default requests; it does not disable caching globally.
I can send a small PR for this.