PermissionDenied errors despite allow-net=* in Deno Deploy

When deploying a Deno script to Deno Deploy with the flag allow-net=*, the build logs sometimes show PermissionDenied errors for network requests, even though the same script runs successfully locally with the same flag.

The goal is to determine whether the wildcard pattern is fully supported for network permissions in Deno Deploy’s runtime, or if additional configuration is required to achieve unrestricted outbound access.

Consider the differences between local Deno execution and the Deploy sandbox, the exact version of Deno Deploy being used, and any documented limitations on pattern matching for allow-net.

• Does the allow-net=* pattern grant access to all hosts in Deno Deploy, or are certain hosts excluded?
• If the wildcard is incomplete, what specific host patterns or additional flags are needed to avoid PermissionDenied?
• Are there version‑specific notes or release‑dependent changes that affect wildcard network permissions?