{"version":"2.1.323","anchor":"http-hook-address-blocking-reworked-with-a-new-error-messag","canonical_anchor":"http-hook-address-blocking-reworked-with-a-new-error-messag","heading":"HTTP hooks to private addresses are blocked with a clearer error","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/http-hook-address-blocking-reworked-with-a-new-error-messag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### HTTP hooks to private addresses are blocked with a clearer error\n\nClaude Code now checks every address an HTTP hook resolves to and blocks private ones with a clear error, while localhost still works\n\n**Unclear.** It is not stated whether this blocking always applies or only under certain settings or policies.\n\n**What**\n\nAn HTTP hook is a step you configure that makes Claude Code send a web request at a certain moment. Claude Code already stopped these hooks from reaching private or local network addresses, and that check has changed:\n\n- Every address a hook's web address leads to is now checked, not just one.\n\n- Blocked requests fail with the error code `ERR_HTTP_HOOK_BLOCKED_ADDRESS`.\n\n- Cloud metadata addresses and some translated (NAT64) addresses appear to be covered too.\n\n- Loopback, meaning your own computer (127.0.0.1 and ::1), is still allowed.\n\n**Why**\n\nA hook pointed at a private or metadata address now gets blocked with an error that says why. Hooks aimed at a server on your own machine keep working for local development.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}