Re: [whatwg/fetch] Add ability to opt-out of back-forward cache (Issue #1917)

KthProg left a comment (whatwg/fetch#1917)

> I'm not sure exactly what you are suggesting here. The bfcache relates to how `Document` objects get instantiated, it doesn't really relate to individual fetches.

From what I saw, bfcache - in caching the entire Document - also caches the results of any fetch requests, at least on Safari. Is this just a Safari bug? I don't remember the exact behavior but I believe when a user back navigated, the fetch requests were replayed and the results were pulled from the cache. This solution worked, which makes me think bfcache was involved:

> You can listen to the pageshow event and check if the page was persisted, and trigger your API request

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1917#issuecomment-6741950256
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1917/6741950256@github.com>