Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Web fetch validates proxy-reported redirect targets

You'll notice
Useful2 Signal2
Web Fetch

Web fetch now rejects malformed redirect destinations from the proxy instead of following them.

What

Before following a destination reported by the fetch proxy, the URL is parsed and normalised. An unparseable destination now raises a PROXY_BAD_RESPONSE error rather than being passed on as a redirect target.

Details
  • The same-origin check runs against the normalised URL, not the raw string.
Evidence

proxy reported a destination that is not a valid URL

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →