-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upbugSomething isn't workingSomething isn't workingeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)status/readyReady to be workedReady to be worked
Description
No matter how many times I refresh a page, I cannot get cached response HIT
to show in the logs. We should probably be using a persistent blockstore instead and this would solve most of our problems.
I believe cache.put(cacheKey, resp) and cache.match(cacheKey)
will not work because of the way the browser cache works... but I also think we have a bug in some mutable checks..
also, fetchAndUpdateCache is always passing mutable=true with await storeReponseInCache({ response, isMutable: true, cacheKey, event })
which can cause cache misses because it's always writing to the mutable cache, instead of the immutable cache when protocol=ipfs
cache workflow needs seriously cleaned up
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upbugSomething isn't workingSomething isn't workingeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/intermediatePrior experience is likely helpfulPrior experience is likely helpfulkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)status/readyReady to be workedReady to be worked