We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When an OData route could be matched, but no route matches the specified the API version, then the controller should return 400 instead of 404.
For example:
/orders?api-version=1.0
This route exists and returns 200.
/orders?api-version=2.0
This route does not exist, but the route ~/orders could exist. The response in this case should be 400 and not 404.
~/orders
The text was updated successfully, but these errors were encountered:
User-defined and out-of-the-box OData controllers now return 400 inst…
9b7a1cc
…ead of 404 when a route could match, but doesn't for a specific API version. Fixes #17
154c489
commonsensesoftware
No branches or pull requests
When an OData route 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
~/orders
could exist. The response in this case should be 400 and not 404.The text was updated successfully, but these errors were encountered: