{"version":"2.1.232","anchor":"web-fetch-validates-proxy-reported-redirect-targets","canonical_anchor":"web-fetch-validates-proxy-reported-redirect-targets","heading":"Web fetch validates proxy-reported redirect targets","tier":"notice","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/web-fetch-validates-proxy-reported-redirect-targets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Web fetch validates proxy-reported redirect targets\n\nWeb fetch now rejects malformed redirect destinations from the proxy instead of following them.\n\n**What**\n\nBefore 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.\n\n**Details**\n\n- The same-origin check runs against the normalised URL, not the raw string.\n\n**Evidence**\n\n`proxy reported a destination that is not a valid URL`\n\n- Area: Web Fetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}