RequestInit is missing some properties like 'cache'

[seeekr]

RequestInit is missing some properties like 'cache'

[seeekr]

Hmm, it seems that this is intentional, as in the CF workers Request API doesn't actually support changing how the fetch() call should interact with the cache. That is a bummer... It's kinda hard to reliably navigate and use the workers APIs with what feels like so many limitations and things you have to pay special attention to and understand in detail before it'll do the simple things you need it to do...

And though the documentation is quite good overall, I feel like I'm stumbling waaay too much still. Might just be me, don't know.

[KianNH]

The Fetch Web API has a few properties or options that aren’t relevant to the server-side context of Workers so they’re not implemented - like mode, credentials, etc

[seeekr]

@KianNH Thanks, omitting those makes sense. But what about the cache property specifically? It would be pretty great to be able to tell CF how it should behave regarding caching for a particular fetch() call. This question might be a product question, but maybe you (or someone else) knows what the current thinking here is, and/or if this particular property just has been forgotten about in some fashion but there's no reason not to implement and provide it?

Thanks again!