Add global_fetch_strictly_public to the Next template for workers
#9087
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fetching from the same worker (more generally a worker in the same zone) fails for deployed workers without this flag. Adding this flag makes sense when there is no origin server - probably we should consider adding it for all frameworks?
(note that same worker fetch works with wrangler dev)
Our current workaround is to create a service binding in wrangler.jsonc - this PR will allow to simplify the config.
Ref:
global_fetch_strictly_publicto the correct folder cloudflare-docs#22017/cc @conico974 @james-elicx