In the last few weeks we have encountered a customer reports of performance issues with their Web API applications.
When the 4th report exhibited the same phenomenon I figured it’s time to blog about it.
Why would you customize a controller selector? (hint – try not to) It gives you a chance to control how the request gets routed. By default Web API uses the controller token from routing to select the controller. If you want a different behavior, such as selection based on an HTTP header, then you need to customize the controller selector.
Wait. Not really. This was true for Web API 1.0. In Web API 2.0 attribute routing and inline constraints were added, with further enhancements in Web API 2.1 and Go to the complete details ...