Skip to content

OData Controller Should Return 400 Instead of 404 #17

New issue

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

Closed
commonsensesoftware opened this issue Sep 12, 2016 · 0 comments
Closed

OData Controller Should Return 400 Instead of 404 #17

commonsensesoftware opened this issue Sep 12, 2016 · 0 comments
Assignees
Labels

Comments

@commonsensesoftware
Copy link
Collaborator

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.

@commonsensesoftware commonsensesoftware self-assigned this Sep 12, 2016
commonsensesoftware pushed a commit that referenced this issue Sep 14, 2016
…ead of 404 when a route could match, but doesn't for a specific API version. Fixes #17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant