Closed nssidhu closed 4 years ago
@nssidhu thanks for contacting us.
That is because Blazor WebAssembly uses a catch-all route to let the client handle non-existing routes and you are likely registering the default fallback route.
I would suggest the following options if you want to get a 404:
This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.
See our Issue Management Policies for more information.
using Blazor WebAssembly as hosted solution. When i call an non exisitng route in the api i get back 200 with index.html, expecting that it should returnlt in API error that route does not exisit.
The actual response returned is, which turns out to be(index.html) 200, success, whereas it is no where what i expect