{"version":"2.1.224","anchor":"sandbox-network-denials-now-tell-you-why","canonical_anchor":"sandbox-network-denials-now-tell-you-why","heading":"Sandbox network denials now tell you why","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-network-denials-now-tell-you-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox network denials now tell you why\n\nBlocked network calls in the sandbox now tell you the host, port and reason.\n\n**What**\n\nWhen the sandbox blocks an outbound connection, it records a violation naming the host, the port and a reason instead of silently failing. Reasons include sandbox policy unavailable, malformed host, host is on the deny list, host is not on the allow list, user denied, and permission prompt failed.\n\n**Details**\n\n- Blocked HTTP requests get their own violation line with the URL query string redacted.\n- A per-domain reason override can be supplied through `deniedDomainReasons`.\n- Domain rules can now carry a `:port` suffix, matched against the port of the connection.\n\n**Evidence**\n\n`host is not on the allow list`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 1\/5"}