{"version":"2.1.321","anchor":"http-hooks-blocked-address-check-telemetry-on-but-blocking","canonical_anchor":"http-hooks-blocked-address-check-telemetry-on-but-blocking","heading":"HTTP hooks are checked for blocked network addresses","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/http-hooks-blocked-address-check-telemetry-on-but-blocking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### HTTP hooks are checked for blocked network addresses\n\nClaude Code now checks HTTP hook addresses against blocked ranges and records hits, but refuses the hook only when a server switch is on\n\n**What**\n\nAn HTTP hook is a hook that sends data to a web address at a set moment in a session. When no proxy is in use, Claude Code now checks the hook's address against a list of blocked address ranges before sending. A proxy here means the sandbox's proxy or one set in your environment.\n\nWhen the address falls in a blocked range:\n\n- Claude Code always records it in usage data, with the reason, the hook's source and the mode.\n\n- It refuses to send the hook only when a server-controlled switch is on. That switch is off unless it is turned on remotely.\n\nClaude Code also now uses its own address lookup whenever no proxy is in use.\n\n**Why**\n\nThis guards against hooks being pointed at addresses they should not reach, such as private network ones. By default it only records such cases rather than stopping them.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}