Skip to content

OData Controller Should Return 400 Instead of 404 #17

Closed
@commonsensesoftware

Description

@commonsensesoftware

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.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions