37. DH story URLs with non-ASCII characters loop on 301 — Low (DH)
Added 16 Nov 2026. Found through the URL Inspection sample ("Redirect error" on 2 of 100 never-shown stories, checks/traffic_funnel/inspect_dh_2026-11-13.md).
What: a story whose slug has a non-ASCII character (el-niño, kraków, létape) redirects to its percent-encoded self forever: …/el-ni%C3%B1o-…-4206975 → 301 → same URL (live 16 Nov 2026, 8 hops then loop). The article is unreachable for users and Google. 7 of 12,262 DH stories published 7 Sep – 5 Nov 2026 (stories_dh_2026-11-13.json). PV's 8 such URLs return 200 (no equivalent middleware).
Cause: story-redirect middleware in tpml-dh app/server/app.js (~354–394 @ upstream/main 47a7e85e) compares req._parsedUrl.pathname (percent-encoded) with /${story.slug} (decoded); they never match, so it always redirects.
🛠️ Fix: compare decodeURIComponent(storyPathName) with /${storySlug}, and redirect to encodeURI("/" + storySlug). Also ask the desk / slug generator to transliterate to ASCII. Verify: curl -sI on …/weak-monsoon-el-ni%C3%B1o-…-4205618 returns 200.
Update (18 Nov 2026, Page indexing export): Search Console lists 111 DH URLs as "Redirect error" (98 on 21 Aug; indexing/2026-11-18/dh-redirect-error/Table.csv). 80 of 111 contain non-ASCII characters: curly quotes ’ (40) and ‘ (21), ñ (13), é (10) and other accented letters. Most are old .html story URLs with quotes in the slug, so the loop affects old stories too, not only the 7 recent ones. Several of the rest have a space or line break inside the slug (…-Development \nCorporation-…-923648.html), probably the same encode/decode mismatch. The fix above covers both; re-check this count ~4 weeks after it ships.