daan944
daan944
Up for discussion: If you don't consider coalescing a breaking change, I could modify the existing cache behavior instead. The main difference is: cache will only cache successful calls and...
Hi @lholmquist the branch is up to date with main, can I do anything else to help this PR along? (Or should I just be more patient ;)? ). Thanks.
Awesome! thanks :) I hope to issue a PR for the types at https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/opossum tomorrow.
I see there's one issue with coalesce: the cachekey is only generated when the 'normal' cache is enabled too. Am working on a fix and will create new PR.
I see 2 routes to fix this: 1. re-write the cache revalidation handler. Upon reading the code, I think there's more amiss there. I suspect a 304 from the backend...
After further investigation: the 304 did not invalidate the cache, just kept as-is. That means that stale-while-revalidate window was extending max-age while sending (useless) revalidation requests to backend. Anyway, fixed...