Skip to main content

DEFAULT_COMPATIBILITY_FLAGS

Constant DEFAULT_COMPATIBILITY_FLAGS 

Source
pub const DEFAULT_COMPATIBILITY_FLAGS: &[&str];
Expand description

#1890: the compatibility flags every emitted Worker carries, ahead of the project’s own (bynk.toml’s [workers] compatibility_flags).

global_fetch_strictly_public makes fetch() to a URL go out over the public internet even when the URL is another Worker on the same account or zone. Without it Cloudflare refuses such a fetch (error 1042, or a fast 404 from a workers.dev sibling), so a Bynk Fetch to a sibling service’s public URL failed where the same URL worked from outside. In Bynk, Fetch to a URL means over the public internet, which is exactly this flag’s behaviour. Worker-to-Worker calls inside one project use Service Bindings, which the flag leaves alone.

Reviewed with COMPATIBILITY_DATE (design/bynk-release-discipline.md, Part 3): a date bump can turn a flag on by default, which makes it redundant here.