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
When an ASP.NET Core route that also uses URL segment API versioning could be matched, but no route matches the specified the API version, then the controller should return 400 instead of 404.
For example:
/v1/orders
This route exists and returns 200.
/v2/orders
This route does not exist, but the route ~/v{version}/orders could exist. The response in this case should be 400 and not 404.
The text was updated successfully, but these errors were encountered:
When an ASP.NET Core route that also uses URL segment API versioning could be matched, but no route matches the specified the API version, then the controller should return 400 instead of 404.
For example:
This route exists and returns 200.
This route does not exist, but the route
~/v{version}/orders
could exist. The response in this case should be 400 and not 404.The text was updated successfully, but these errors were encountered: