Skip to main content

Timeline for WebAPI Controllers not being found

Current License: CC BY-SA 4.0

11 events
when toggle format what by license comment
Dec 7, 2022 at 1:53 review Suggested edits
Dec 7, 2022 at 3:38
Dec 6, 2022 at 16:01 answer added Towhidul Islam Tuhin timeline score: 0
Oct 5, 2020 at 12:54 history edited Mark Cassidy CC BY-SA 4.0
edited title
Mar 10, 2020 at 1:24 answer added Pankaj Vats timeline score: 1
May 31, 2019 at 14:16 vote accept Ben Lipson
Feb 6, 2018 at 14:54 answer added Ben Lipson timeline score: 16
Feb 6, 2018 at 14:26 comment added Corey Smith Are you using a dependency injection framework other than Microsoft.Extensions.DependencyInjection? I've got a solution on a clean install of Sitecore 8.2 Update-6 with your code that returns a different error message than you're seeing due to a missing HttpGet attribute: Error message received at /-/api is: "Message": "The requested resource does not support http method 'GET'.". My solution also has 69 controllers registered (the 68 you mentioned + the custom one from your question), which makes me think something else in your Initialize pipeline is causing issues.
Feb 6, 2018 at 13:57 comment added Ben Lipson Registering it after that line did not work
Feb 6, 2018 at 5:44 answer added jammykam timeline score: 1
Feb 6, 2018 at 4:55 comment added Corey Smith What happens if you register your pipeline processor after Sitecore.Cintel.Endpoint.Plumbing.InitializeRoutes, Sitecore.Cintel? Several of the processors after InitializeCommandRoute make big changes to the Web API configuration, so it's possible your changes are being overwritten. If that fixes it, you'll also need to add an HttpGet attribute to your Test action, otherwise you'll get another error about the requested resource not supporting the "GET" HTTP method.
Feb 5, 2018 at 23:12 history asked Ben Lipson CC BY-SA 3.0