SDammann.WebApi.Versioning
SDammann.WebApi.Versioning copied to clipboard
Versioning support for ASP.NET Web Api
The error messages generated by the VersionedControllerSelector class could be configurable. I think the message "The API 'Version2_2.values' doesn't exist" exposes to much information. if we where able to supress...
No documentation available for versioned API's.
URLs are assumed to be versioned in the route.
Currently POST methods are formatted this way: POST api/v2/Hello/message={message}&otherthing={otherthing} They should look like this: POST api/v2/Hello?message={message}&otherthing={otherthing} This also causes a yellow screen of death when clicking on the original url.
The new Attribute routing from WebAPI 2 is not supported. [HttpGet("api/home/{id:int}/details")] Public string Details(int id) { // } Current output: GET api/v1/Home?id={id} Expected output: GET api/v1/Home/{id}/details
I use AcceptHeaderVersionedControllerSelector system. I would a default version if a client don't send accept header ? Is it possible the use a major.minor pattern with AcceptHeaderVersionedControllerSelector or is only...
The relationship between `AcceptHeaderVersionedControllerSelector` and ASP.NET's logic for actually serializing the http response body is a bit strange. You can cause some strange situations with a header like `Accept: application/json;...