You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Web FetchArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
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.
