Help center redirect resolution fails when locale-prefixed URLs are introduced before matching

Redirect resolution on help center custom domains can fail when the incoming request URL is rewritten to include a locale prefix before redirect matching is performed.

In these cases, a redirect rule may be configured correctly for the original source path, but matching is attempted against the rewritten locale-prefixed path instead, causing the rule to be missed and the visitor to reach a 404 page.

A temporary workaround is to create duplicate redirect rules for both the original and locale-prefixed source URLs.

Intended action:
A redirect rule for /old-path should send visitors to the new help center article.

Actual behavior:
When a locale prefix is added to the incoming URL before redirect matching, the system looks up /<locale>/old-path instead of /old-path, so the redirect rule is not matched and the visitor gets a 404.