405 method not allowed Web API

Question

This error is very common  and I tried all of the solutions and non of them worked  I have disabled WebDAV publishing in control panel and added this to my web config file      lt handlers gt     lt remove name  WebDAV   gt     lt  handlers gt     lt modules runAllManagedModulesForAllRequests  true  gt     lt remove name  WebDAVModule   gt     lt  modules gt    The error still persists  This is the controller      static readonly IProductRepository repository   new ProductRepository         public Product Put Product p                return repository Add p           Method implementation    public Product Add Product item                if  item    null                        throw new ArgumentNullException  item                      item Id    nextId            products Add item           return item          And this is where the exception is thrown   client BaseAddress   new Uri  http   localhost 5106     client DefaultRequestHeaders Accept Add  new MediaTypeWithQualityHeaderValue  application json           var response   await client PostAsJsonAsync  api products   product    405 exception   Any suggestions

User · Answer

I was having exactly the same problem  I looked for two hours what was wrong with no luck until I realize my POST method was private instead of public     Funny now seeing that error message is kind of generic  Hope it helps

User · Answer

I m late to this party but as nothing above was either viable or working in most cases  here is how this was finally resolved for me   On the server the site service was hosted on  a feature was required  HTTP ACTIVATION        Server Manager   Manage   Add Roles and Features   next next next till you get to Features   Under  NET  each version  tick HTTP Activation    Also note there is one hidden under  net   WCF Services    This then worked instantly  That was melting my brain

User · Answer

In my case I had a physical folder in the project with the same name as the WebAPI route  ex  sandbox  and only the POST request was intercepted by the static files handler in IIS  obviously     Getting a misleading  405 error instead of the more expected 404  was the reason it took me long to troubleshoot   Not easy to fall-into this  but possible  Hope it helps someone

User · Answer

I could NOT solve this   I had CORS enabled and working as long as the POST returned void  ASP NET 4 0 - WEBAPI 1    When I tried to return a HttpResponseMessage  I started getting the HTTP 405 response   Based on Llad s response above  I took a look at my own references     I had the attribute  System Web Mvc HttpPost  listed above my POST method     I changed this to use     System Web Http HttpPostAttribute   HttpOptions  public HttpResponseMessage Post object json                        return new HttpResponseMessage   StatusCode   HttpStatusCode OK        This fixed my woes   I hope this helps someone else     For the sake of completeness  I had the following in my web config     lt httpProtocol gt       lt customHeaders gt           lt clear   gt           lt add name  Access-Control-Expose-Headers   value  WWW-Authenticate   gt           lt add name  Access-Control-Allow-Origin  value       gt           lt add name  Access-Control-Allow-Methods  value  GET  POST  OPTIONS  PUT  PATCH  DELETE    gt           lt add name  Access-Control-Allow-Headers  value  accept  authorization  Content-Type    gt           lt remove name  X-Powered-By    gt       lt  customHeaders gt   lt  httpProtocol gt

User · Answer

For my part my POST handler was of this form    HttpPost   routeParam     public async Task lt ActionResult gt  PostActuality   FromRoute  int routeParam   FromBody  PostData data    I figured out that I had to swap the arguments  that is to say the body data first then the route parameter  as this    HttpPost   routeParam     public async Task lt ActionResult gt  PostActuality   FromBody  PostData data   FromRoute  int routeParam

User · Answer

Another possible issue which causes the same behavior is the default parameters in the routing  In my case the controller was located and instantiated correctly  but the POST was blocked because of default Get action specified   config Routes MapHttpRoute      name   GetAllRoute       routeTemplate   api  controller   ext          defaults  new   action    Get         this was causing the issue

User · Answer

We had a similar issue  We were trying to GET from    RoutePrefix  api car    public class CarController  ApiController        HTTPGet       Route          public virtual async Task lt ActionResult gt  GetAll                So we would  GET   api car   and this would throw a 405 error    The Fix   The CarController cs file was in the directory  api car so when we were requesting this api endpoint  IIS would send back an error because it looked like we were trying to access a virtual directory that we were not allowed to    Option 1  change   rename the directory the controller is in Option 2  change the route prefix to something that doesn t match the virtual directory

User · Answer

Here is one solution     lt handlers accessPolicy  Read  Script  gt      lt remove name  WebDAV    gt   lt  handlers gt   docs microsoft com solution article  and remove WebDAV from modules   lt remove name  WebDAVModule    gt

User · Answer

I tried many thing to get DELETE method work  I was getting 405 method not allowed web api    and finally I added  Route  api scan  id      to my controller and was work fine   hope this post help some one           DELETE api Scan 5      Route  api scan  id          ResponseType typeof Scan        public IHttpActionResult DeleteScan int id                Scan scan   db Scans Find id           if  scan    null                        return NotFound                       db Scans Remove scan           db SaveChanges             return Ok scan

User · Answer

check in your project  csproj file and change    lt IISUrl gt http   localhost PORT  lt  IISUrl gt    to your website url like this   lt IISUrl gt http   example com applicationName  lt  IISUrl gt

User · Answer

Chrome often times tries to do an OPTIONS call before doing a post  It does this to make sure the CORS headers are in order  It can be problematic if you are not handling the OPTIONS call in your API controller   public void Options

User · Answer

HttpPost  is unnecessary    Route      public void Post ProductModel data

User · Answer

Old question but none of the answers worked for me  This article solved my problem by adding the following lines to web config   lt system webServer gt     lt modules runAllManagedModulesForAllRequests  quot false quot  gt       lt remove name  quot WebDAVModule quot    gt     lt  modules gt   lt  system webServer gt

User · Answer

This error can also occur when you try to connect to http while the server is on https    It was a bit confusing because my get-requests were OK  the problem was only present with post-requests

User · Answer

You can also get the 405 error if say your method is expecting a parameter and you are not passing it   This does NOT work    405 error   HTML View Javascript    ajax            url    api News                      Web Api   public HttpResponseMessage GetNews int id    Thus if the method signature is like the above then you must do   HTML View Javascript    ajax            url    api News 5

User · Answer

Make sure your controller inherits from Controller class   It might even be crazier that stuff would work locally even without that

User · Answer

If you have a route like   Route  nuclearreactors  reactorId       You need to use the exact same parameter name in the method e g    public ReactorModel GetReactor reactorId             If you do not pass the exact same parameter you may get the error  405 method not allowed  because the route will not match the request and WebApi will hit a different controller method with different allowed HTTP method

User · Answer

You are POSTing from the client   await client PostAsJsonAsync  api products   product     not PUTing    Your Web API method accepts only PUT requests   So   await client PutAsJsonAsync  api products   product

User · Answer

This does not answer your specific question  but when I had the same problem I ended up here and I figured that more people might do the same   The problem I had was that I had indeliberately declared my Get method as static  I missed this an entire forenoon  and it caused no warnings from attributes or similar   Incorrect   public class EchoController   ApiController       public static string Get                 return string Empty            Correct   public class EchoController   ApiController       public string Get                 return string Empty

User · Answer

I had the same exception   My problem was that I had used   using System Web Mvc     Wrong namespace for HttpGet attribute            HttpGet  public string Blah         return  blah       SHOULD BE  using System Web Http     Correct namespace for HttpGet attribute            HttpGet  public string Blah         return  blah

User · Answer

My problem turned out to be Attribute Routing in WebAPI  I created a custom route  and it treated it like a GET instead of WebAPI discovering it was a POST       Route           HttpPost    I added this attribute explicitly  and it worked     public void Post ProductModel data                            I knew it had to be something silly  that consumes your entire day

User · Answer

I was getting the 405 on my GET call  and the problem turned out that I named the parameter in the GET server-side method Get int formId   and I needed to change the route  or rename it Get int id

[c#] 405 method not allowed Web API

Examples related to c#

Examples related to asp.net-web-api

Examples related to webdav