Had a website that has been working fine suddenly have issues in various places where we have controllers that do a Response.Redirect on paths that are arabic urls.
I think it’s just where there are multiple path segments /some/path. And it’s seemingly only happening on Azure (hosted on a Windows Webapp) - can’t recreate locally.
Because I can’t recreate locally I assume its a Kestrel rule - tightening of not having encoded urls. Has anyone seen similar? Trying to work out when this started happening - and why!
For anyone suffering we saw URLS with malformed chars (seeming where the slash had been mis encoded with the neighbouring characters?) - our workaround was to use Cloudflare page redirects to detect these broken, malformed urls and just point them in the correct place. Longer term I’m going to write a helper to encode arabic url paths properly before passing to Redirect()
Steve