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
Controllers that use convention-based routing do not always return 400 for actions that match in some API versions, but not others.
For example:
[ApiVersion( "1.0" )] public class MyController : ApiController { public IHttpActionResult Get() => Ok(); } [ApiVersion( "2.0" )] public class My2Controller : ApiController { public IHttpActionResult Get() => Ok(); public IHttpActionResult Patch() => StatusCode( HttpStatusCode.NoContent ); } [ApiVersion( "3.0" )] public class My3Controller : ApiController { public IHttpActionResult Get() => Ok(); }
The requested routes should produce the following results:
The text was updated successfully, but these errors were encountered:
Updates 400 responses to use the standard error response format with …
37a5f44
…support to change the format. Fixes #26
239ec61
Return 400 instead of 404 for action that can match in at least one A…
678224e
…PI version. Fixes #26
144ed88
commonsensesoftware
No branches or pull requests
Controllers that use convention-based routing do not always return 400 for actions that match in some API versions, but not others.
For example:
The requested routes should produce the following results:
The text was updated successfully, but these errors were encountered: