Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative to the cache: no-cache in fetchClient #206

Open
n3oney opened this issue Jun 18, 2024 · 3 comments
Open

Alternative to the cache: no-cache in fetchClient #206

n3oney opened this issue Jun 18, 2024 · 3 comments

Comments

@n3oney
Copy link

n3oney commented Jun 18, 2024

Hi, 04034e2 has introduced using the cache: "no-cache" option when making fetch requests. This however, is unsupported by Cloudflare's Workers and Pages, and unfortunately isn't silently ignored, but throws an error. Is it possible to have an option to disable that parameter, or some alternate solution bypassing it?

It currently causes this error: Error: The 'cache' field on 'RequestInitializerDict' is not implemented.

Which is gone by downgrading to 1.0.0-rc.3, which didn't have that commit in.

See cloudflare/workerd#698 (comment)

@bkniffler
Copy link

bkniffler commented Jun 30, 2024

Please... our logs have been silently failing due to this for several weeks. Maybe making the fetch function over writable would help with these kind of issues.
Bildschirmfoto 2024-06-30 um 09 15 47

@multiplehats
Copy link

Yup same issue here

@dasfmi
Copy link
Collaborator

dasfmi commented Aug 9, 2024

Have been waiting for Cloudflare to address this issue in cloudflare/workerd#698 (comment) but there haven't been any updates for a while.

The reason I added this cache parameter is to prevent frameworks like Next.js from caching the requests. Will have to think about a different solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants