Asp NET Web API - 405 - HTTP verb used to access this page is not allowed - how to set handler mappings

Question

I wrote REST service using ASP NET Web API  I m trying to send HttpDelete request  however I get the following error      405 - HTTP verb used to access this page is not allowed   I think I m close to the solution  I found out that I should enable IIS remote management   go to Handler Mappings section and add DELETE verb to the appropriate position    but the problem is that there is a lots of different positions on the list     sth like here  http   www somacon com p126 php    Which one should I edit   Few of them don t have extension  e g   ExtensionUrlHandler-Integrated-4 0  and I added DELETE verb to it  but it still doesn t work     It was just a shot in the dark to modify that one  so should I modify different position  If so  which one  Or maybe is there anything more what I should do   The same web service work perfectly fine on my local service  so I guess the problem is with the remote IIS     Greetings

User · Answer

I had this problem and I solved the following:

open IIS
Select the Backend Site
in features view: open Handler Mapping

in the Handler Mapping window, Find WebDAV

in Edit Module Mapping, open Request Restrictions

User · Answer

Change Your Web Config file as below  It will act like charm   In node  lt system webServer gt  add below portion of code   lt modules runAllManagedModulesForAllRequests  true  gt     lt remove name  WebDAVModule   gt   lt  modules gt    After adding  your Web Config will look like below   lt system webServer gt       lt validation validateIntegratedModeConfiguration  false    gt       lt modules runAllManagedModulesForAllRequests  true  gt           lt remove name  WebDAVModule   gt       lt  modules gt       lt httpProtocol gt       lt customHeaders gt           lt add name  Access-Control-Allow-Origin  value       gt           lt add name  Access-Control-Allow-Headers  value  Content-Type    gt           lt add name  Access-Control-Allow-Methods  value  GET  POST  PUT  DELETE  OPTIONS    gt       lt  customHeaders gt       lt  httpProtocol gt       lt handlers gt         lt remove name  ExtensionlessUrlHandler-ISAPI-4 0 32bit    gt         lt remove name  ExtensionlessUrlHandler-ISAPI-4 0 64bit    gt         lt remove name  ExtensionlessUrlHandler-Integrated-4 0    gt         lt add name  ExtensionlessUrlHandler-ISAPI-4 0 32bit  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32  responseBufferLimit  0    gt         lt add name  ExtensionlessUrlHandler-ISAPI-4 0 64bit  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64  responseBufferLimit  0    gt         lt add name  ExtensionlessUrlHandler-Integrated-4 0  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  type  System Web Handlers TransferRequestHandler  preCondition  integratedMode runtimeVersionv4 0    gt       lt  handlers gt   lt  system webServer gt

User · Answer

Besides all above solutions  check if you have the  id  or any custom defined parameter in the DELETE method is matching the route config   public void Delete int id          some code here     If you hit with repeated 405 errors better reset the method signature to default as above and try   The route config by default will look for id in the URL  So the parameter name id is important here unless you change the route config under the App Start folder   You may change the data type of the id though   For example the method below should work just fine   public void Delete string id          some code here     Note  Also ensure that you pass the data over the url not the data method that will carry the payload as body content   DELETE http    url   action   id    Example   DELETE http   localhost item 1   Hope it helps

User · Answer

None of the above worked for me and  i was trouble shooting using a support page https   support microsoft com en-us help 942051 error-message-when-a-user-visits-a-website-that-is-hosted-on-a-server then i compared the application host file with one of the working copy and seems like i was missing a bunch of handlers and when i added back those into application host its start working   I was missing all these    lt add name  xamlx-ISAPI-4 0 64bit  path    xamlx  verb  GET HEAD POST DEBUG  modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64    gt   lt add name  xamlx-ISAPI-4 0 32bit  path    xamlx  verb  GET HEAD POST DEBUG  modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32    gt   lt add name  xamlx-Integrated-4 0  path    xamlx  verb  GET HEAD POST DEBUG  type  System Xaml Hosting XamlHttpHandlerFactory  System Xaml Hosting  Version 4 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  preCondition  integratedMode runtimeVersionv4 0    gt   lt add name  rules-ISAPI-4 0 64bit  path    rules  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64    gt   lt add name  rules-ISAPI-4 0 32bit  path    rules  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32    gt   lt add name  rules-Integrated-4 0  path    rules  verb     type  System ServiceModel Activation ServiceHttpHandlerFactory  System ServiceModel Activation  Version 4 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  preCondition  integratedMode runtimeVersionv4 0    gt   lt add name  xoml-ISAPI-4 0 64bit  path    xoml  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64    gt   lt add name  xoml-ISAPI-4 0 32bit  path    xoml  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32    gt   lt add name  xoml-Integrated-4 0  path    xoml  verb     type  System ServiceModel Activation ServiceHttpHandlerFactory  System ServiceModel Activation  Version 4 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  preCondition  integratedMode runtimeVersionv4 0    gt   lt add name  svc-ISAPI-4 0 64bit  path    svc  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64    gt   lt add name  svc-ISAPI-4 0 32bit  path    svc  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32    gt   lt add name  svc-Integrated-4 0  path    svc  verb     type  System ServiceModel Activation ServiceHttpHandlerFactory  System ServiceModel Activation  Version 4 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  preCondition  integratedMode runtimeVersionv4 0    gt   lt add name  rules-64-ISAPI-2 0  path    rules  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness64    gt   lt add name  rules-ISAPI-2 0  path    rules  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness32    gt   lt add name  rules-Integrated  path    rules  verb     type  System ServiceModel Activation HttpHandler  System ServiceModel  Version 3 0 0 0  Culture neutral  PublicKeyToken b77a5c561934e089  preCondition  integratedMode runtimeVersionv2 0    gt   lt add name  xoml-64-ISAPI-2 0  path    xoml  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness64    gt   lt add name  xoml-ISAPI-2 0  path    xoml  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness32    gt   lt add name  xoml-Integrated  path    xoml  verb     type  System ServiceModel Activation HttpHandler  System ServiceModel  Version 3 0 0 0  Culture neutral  PublicKeyToken b77a5c561934e089  preCondition  integratedMode runtimeVersionv2 0    gt   lt add name  svc-ISAPI-2 0-64  path    svc  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework64 v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness64    gt   lt add name  svc-ISAPI-2 0  path    svc  verb     modules  IsapiModule  scriptProcessor   windir  Microsoft NET Framework v2 0 50727 aspnet isapi dll  preCondition  classicMode runtimeVersionv2 0 bitness32    gt   lt add name  svc-Integrated  path    svc  verb     type  System ServiceModel Activation HttpHandler  System ServiceModel  Version 3 0 0 0  Culture neutral  PublicKeyToken b77a5c561934e089  preCondition  integratedMode runtimeVersionv2 0    gt

User · Answer

I ve had this happen  405 method not allowed  when the web api post method I was calling had primitive types for parameters  instead of a complex type that was accessed from the body  Like so   This worked     Route  update    Authorize  HttpPost    public int Update  FromBody  updateObject update    This didn t     Route  update    Authorize  HttpPost   public int Update string whatever  int whatever  string whatever

User · Answer

Uncommon but may help some      ensure you re using  HttpPut  from System Web Http   We were getting a  Method not allowed  405  on a HttpPut decorrated method   Our problem would seem to be uncommon  as we accidentally used the  HttpPut  attribute from System Web Mvc and not System Web Http  The reason being  resharper suggested the  Mvc version  where-as usually System Web Http is already referenced when you derive directly from ApiController we were using a class that extended ApiController

User · Answer

If it is IIS 8 0 check if HTTP Activation is enabled   Server manager -  IIS -  Manage  see right top  -  Add Roles and Features -      -  get to WCF configuration and then select HTTP Activation

User · Answer

Change Your Web Config file as below    lt system webServer gt   lt validation validateIntegratedModeConfiguration  false   gt   lt modules runAllManagedModulesForAllRequests  true  gt   lt remove name  WebDAVModule    gt   lt  modules gt   lt handlers gt   lt remove name  WebDAV   gt   lt remove name  ExtensionlessUrlHandler-Integrated-4 0   gt   lt remove name  OPTIONSVerbHandler   gt   lt remove name  TRACEVerbHandler   gt   lt add name  ExtensionlessUrlHandler-Integrated-4 0  path      verb     type  System Web Handlers TransferRequestHandler  preCondition  integratedMode runtimeVersionv4 0    gt   lt  handlers gt   lt  system webServer gt

User · Answer

You don t need to uninstall WebDAV  just add these lines to the web config    lt system webServer gt     lt modules gt       lt remove name  WebDAVModule    gt     lt  modules gt     lt handlers gt       lt remove name  WebDAV    gt     lt  handlers gt   lt  system webServer gt

User · Answer

If none of the above solutions solved your issue like in my case  still stuck with my RestClient module facing 405   try to request your Api with a tool like Postman or Fiddler  I mean the problem may be elsewhere like a bad formatted request    I discover that my RestClient module was asking a  Put  with an Id paremeter  not well formatted     http   myserver api someresource id 75fd954d-d984-4a31-82fc-8132e1644f78   instead of  http   myserver api someresource 75fd954d-d984-4a31-82fc-8132e1644f78   Incidiously  bad formatted request returns 405 - Method Not Allowed  IIS 7 5

User · Answer

Common cause for this error is WebDAV  Make sure you uninstall it

User · Answer

I will add for those that get stuck trying to run PHP  Laravel in may case  or other unique IIS hosting situation with the 405 error  that you need to change the verbs in the handler for that for that specific situation    so since I was using PHP I went to the PHP handler and in the Request Restrictions  then Verbs tab  add the verbs you need  This was all I needed to add to the web config to enable CORS in Laravel    lt handlers gt     lt remove name  php-5 6 40    gt     lt add name  php-5 6 40  path    php  verb  GET HEAD POST PUT DELETE OPTIONS  modules  FastCgiModule  scriptProcessor  C  Program Files  x86  PHP v5 6 php-cgi exe  resourceType  Either  requireAccess  Script    gt   lt  handlers gt

User · Answer

This error is coming from the staticfile handler -- which by default doesn t filter any verbs  but probably can only deal with HEAD and GET   And this is because no other handler stepped up to the plate and said they could handle DELETE   Since you are using the WEBAPI  which because of routing doesn t have files and therefore extensions  the following additions need to be added to your web config file    lt system webserver gt       lt httpProtocol gt           lt handlers gt                             lt remove name  ExtensionlessUrlHandler-ISAPI-4 0 32bit    gt               lt remove name  ExtensionlessUrlHandler-ISAPI-4 0 64bit    gt               lt remove name  ExtensionlessUrlHandler-Integrated-4 0    gt                lt add name  ExtensionlessUrlHandler-ISAPI-4 0 32bit  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  modules  IsapiModule  scriptProcessor  C  windows Microsoft NET Framework v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness32  responseBufferLimit  0    gt               lt add name  ExtensionlessUrlHandler-ISAPI-4 0 64bit  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  modules  IsapiModule  scriptProcessor  C  windows Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64  responseBufferLimit  0    gt               lt add name  ExtensionlessUrlHandler-Integrated-4 0  path      verb  GET HEAD POST DEBUG PUT DELETE PATCH OPTIONS  type  System Web Handlers TransferRequestHandler  preCondition  integratedMode runtimeVersionv4 0    gt    Obviously what is needed depends on classicmode vs integratedmode  and classicmode depends on bitness   In addition  the OPTIONS header has been added for CORS processing  but if you don t do CORS you don t need that   FYI  your web config is the local to the application  or application directory  version whose top level is applicationHost config

User · Answer

In our case  the problem was with federated signon between a  Net site and ADFS   When redirecting to the ADFS endpoint the wctx parameter needed all three parameters for the  WSFederationAuthenticationModule CreateSignInRequest method  rm  id  and ru  Thanks to Guillaume Raymond for the tip to check the URL parameters

[asp.net] Asp.NET Web API - 405 - HTTP verb used to access this page is not allowed - how to set handler mappings

Examples related to asp.net

Examples related to asp.net-mvc

Examples related to iis

Examples related to iis-7

Examples related to asp.net-web-api