{"version":"2.1.232","anchor":"two-silently-broken-gateway-configs-now-warn-at-boot","canonical_anchor":"two-silently-broken-gateway-configs-now-warn-at-boot","heading":"Two silently broken gateway configs now warn at boot","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/two-silently-broken-gateway-configs-now-warn-at-boot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Two silently broken gateway configs now warn at boot\n\nTwo gateway config shapes that used to fail invisibly now warn at boot.\n\n**What**\n\nThe gateway warns about two config shapes that used to fail invisibly.\n\n**Details**\n\n- If any policy has a `desktop` overlay but `listen.public_url` is unset, it warns that origin pinning cannot be checked, so an origin-pinned value would be dropped by desktops with no sign of it.\n- If a policy sets `sandbox.network.allowedDomains` to an explicitly empty list, it warns that the derived `coworkEgressAllowedHosts` is not served at all, since desktops treat absent and empty the same.\n\n**Evidence**\n\n`origin-pin hygiene is skipped at boot`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}