Not found routes causes Blazor WASM to reload.

[julianadormon]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

This is in regard to NotFound route causes reload #23100

Not found routes causes Blazor WASM to reload.

Describe the solution you'd like

As per the conversation on the previous issue, it was closed because "this is by design" with the reason that this would give the server a chance to handle the not found response.

This is fine, however I am using a Blazor wasm standalone project and this is happening. This is jarring and not a great user experience.
I feel like the user is getting penalized with the wasm loading screen again.

Thanks for your consideration.

Additional context

No response

[javiercn]

@julianadormon thanks for contacting us.

You can define a page with a catch-all route

NotFound.razor

@page "{**slug}
...

and implement your own logic within it to handle any fallback path not handled by your standalone wasm app.

[dotnet-policy-service]

Hi @julianadormon. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.