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

fix: set cache to no-store instead of no-cache #249

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Conversation

dasfmi
Copy link
Collaborator

@dasfmi dasfmi commented Dec 16, 2024

This fix closes #246; Cloudflare doesn't support no-cache value so this change sets cache to 'no-store' instead.

This fix closes #246; Cloudflare doesn't support no-cache value
so this change sets cache to 'no-store' instead.
@gabrielelpidio gabrielelpidio merged commit a386427 into main Dec 16, 2024
11 checks passed
@gabrielelpidio gabrielelpidio deleted the set-no-store branch December 16, 2024 17:10
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

Successfully merging this pull request may close these issues.

Support no-store vs no-cache on fetchClient to work w Cloudflare workers outside typical node workflow
2 participants