fix(landing): keep mixed-case locale casing in emitted URLs (#562)

Astro's getRelativeLocaleUrl lowercases the locale segment by default, so landing links and hreflang for zh-CN, zh-TW, and pt-BR were emitted lowercase and 404 on case-sensitive Cloudflare Pages. Pin the casing at the localizeHref chokepoint with normalizeLocale: false, add an e2e hreflang casing guard, and add a deploy-time check that blocks the build if any lowercased locale path leaks into the output.

Closes #554
This commit is contained in:
SnapOtter
2026-07-18 10:47:53 +08:00
committed by GitHub
parent 54073a7c50
commit 67f54347b2
3 changed files with 56 additions and 1 deletions
+8 -1
View File
@@ -10,13 +10,20 @@ export const SITE = "https://snapotter.com";
* A trailing "#hash" is split off first and reattached untouched, since
* Astro's URL builder would otherwise treat it as part of the path and
* mangle it with a trailing slash (e.g. "/#pricing" -> "/#pricing/").
*
* `normalizeLocale: false` keeps the locale segment identical to its code.
* By default Astro lowercases it (getRelativeLocaleUrl runs normalizeTheLocale,
* so "zh-CN" -> "zh-cn", "pt-BR" -> "pt-br"), but our routes are built from the
* raw codes (getStaticPaths -> /zh-CN/, /pt-BR/) and the sitemap keeps that same
* mixed case. The lowercased links resolve fine on case-insensitive local hosting
* but 404 on case-sensitive hosts like Cloudflare Pages, so we pin the casing here.
*/
export function localizeHref(locale: string, path: string): string {
const hashIndex = path.indexOf("#");
const pathname = hashIndex === -1 ? path : path.slice(0, hashIndex);
const hash = hashIndex === -1 ? "" : path.slice(hashIndex);
const clean = pathname.startsWith("/") ? pathname.slice(1) : pathname;
return `${getRelativeLocaleUrl(locale, clean)}${hash}`;
return `${getRelativeLocaleUrl(locale, clean, { normalizeLocale: false })}${hash}`;
}
/**