v157 · url host parsing

Migration scanner

Paste the URLs you actually ship — a redirect map, a CDN allowlist, a column out of a CSV — and find out which ones Chrome 157 will refuse to parse, why, and what the corrected form is. Everything runs in this page; nothing is uploaded.

Scan a list

The scanner checks the authority of each URL against the URL Standard's forbidden host code points directly, so it gives the Chrome 157 answer even when you run it on an older build that still accepts these.

Scanned
0
Will break
0
Fine
0
Findings
URLChrome 157whycorrected
Nothing scanned yet.
Paste a list and press Scan.

code path

// The fix is almost always one of three things:
//   - the space was a typo               -> delete it
//   - the space belonged in the path     -> move it, it encodes to %20
//   - the "host" was really a file path  -> use a file:// URL
//
// Percent-encoding a space in the HOST does not rescue it: %20 is a
// legal host character, so "exa%20mple.com" parses — as a hostname
// that does not exist. That is a different bug, not a fix.

see also