You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the routing unification process we switched the way we were
decoding the URL prior to feeding it to routing and that introduced a
small regression in interactive routing compared to .NET 7.0.
This commit fixes that regression by using the same logic for decoding
the URL in the client that is used on the server.
In addition to that, the Blazor router now post processes the URL to
replace instances of `%2F` with `/` when providing values to maintain
the behavior in 7.0 where it used UnescapeDataString.
This also makes the routing on the server and on the client consistent
in their handling of encoded `/` characters.
[UnconditionalSuppressMessage("Trimming","IL2067",Justification="Application code does not get trimmed, and the framework does not define routable components.")]
0 commit comments