{"version":"2.1.224","anchor":"sandbox-network-rules-can-specify-a-port","canonical_anchor":"sandbox-network-rules-can-specify-a-port","heading":"Sandbox network rules can specify a port","tier":"use","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-network-rules-can-specify-a-port","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox network rules can specify a port\n\nSandbox allow and deny rules can now target a specific port instead of the whole host.\n\n**What**\n\nDomain allow and deny rules in the sandbox now parse a host pattern plus an optional port, so a rule can target a single port rather than the whole host.\n\n**Details**\n\n- Matching fails closed on both sides: a port-qualified rule matches a request with an unknown port when denying, and does not match when allowing.\n- Otherwise the port must match exactly.\n- Deny rules still come from `sandbox.network.deniedDomains` plus WebFetch-style `domain:` permission rules.\n\n**Evidence**\n\n`sandbox.network.allowManagedDomainsOnly is set and `\n\n- Area: Sandbox\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}