405 method not allowed in IIS7 5 for PUT method

Question

I use WebClient type to upload   cab files to my server  On the server side  I registered a HTTP handler for   cab file with the PUT method as below     lt add name  ResultHandler  path    cab  verb  PUT  type  FileUploadApplication ResultHandler  resourceType  Unspecified  requireAccess  Script  preCondition  integratedMode    gt    But I always get a  405 method not allowed  error  The response said the allowed methods are as below   Headers    Allow  GET  HEAD  OPTIONS  TRACE Content-Length  1293 Content-Type  text html Date  Fri  27 May 2011 02 08 18 GMT Server  Microsoft-IIS 7 5 X-Powered-By  ASP NET    Even if I explicitly allow the PUT method in the IIS Request Filtering for my web application  the same error still occurs   I suspect this is a IIS related issue  I m hoping someone could shed some light on this for me

User · Answer

Removing the WebDAV-module should be sufficient  Just change your Web config    lt system webServer gt       lt modules runAllManagedModulesForAllRequests  true  gt           lt remove name  WebDAVModule    gt

User · Answer

Often this error is caused by the WebDAV module that try to handle this kind of requests  An easy solution is to remove it from modules and from handlers of the system webServer section just inside your web config file   Here a configuration example    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

I had this problem with WebDAV when hosting a MVC4 WebApi Project  I got around it by adding this line to the web config    lt handlers gt     lt remove name  WebDAV    gt     lt add name  WebDAV  path     verb     modules  WebDAVModule        resourceType  Unspecified  requireAccess  None    gt   lt  handlers gt    As explained here  http   evolutionarydeveloper blogspot co uk 2012 07 method-not-allowed-405-on-iis7-website html

User · Answer

If IIS app pool is running under classic mode  make sure you have the following in your web config   lt remove name  ExtensionlessUrlHandler-ISAPI-4 0 64bit    gt        lt add name  ExtensionlessUrlHandler-ISAPI-4 0 64bit  path      verb  GET HEAD POST DEBUG PUT DELETE  modules  IsapiModule  scriptProcessor  c  Windows Microsoft NET Framework64 v4 0 30319 aspnet isapi dll  preCondition  classicMode runtimeVersionv4 0 bitness64    gt

User · Answer

For me this error wouldn t go away and allow PUT methods  whatever i did   uninstalled webdav  put configuration in web config to remove webdav from handlers and modules  and set up PUT as an allowed verb on the request filters on iis   and ensure iis handler mappings handling the request had PUT configured     My problem was eventually due to bad installation of ASP NET 4 5 Extensions  Removed everything related to asp net from server roles and features  restarted  readded the roles and restarted  everything worked with above config   --- The below will make PUT be accepted  but will send it to the wrong handler  --ignore the below  finally  adding PUT verb as allowed verb on TRACE handler mapping on iis worked   since i had enabled failed error tracing  and this verb was not allowing the verb   last time i had the same problem on another server s IIS  it was due to a missing     at the end of the URL since it was using a default handler without using the default document probably and now i realize that   so check IIS handler mappings if nothing else helps

User · Answer

To prevent WebDav from getting enabled at all  remove the following entry from the ApplicationHost config   lt add name  WebDAVModule    gt   The entry is located in the modules section   Exact location of the config  C  Windows System32 inetsrv config applicationHost config

User · Answer

I had this problem but nothing related to WebDAV was the issue  In my case  the client was sending a POST to www myServer com api chart   This call should be handled by the  ExtensionlessUrlHanlder-Integrated-4 0   however  somehow a local file structure was created in my server directory      Server api chart     This meant that the  StaticFile  handler was being called instead   Deleting those local files finally solved the problem

User · Answer

I had the same problem  with a RESTful API running on aspnet core  I didn t want to uninstall the WebDAV  and I tried most of the remedies described above  I tried to set the verbs  quot   quot  both on the site and on the server itself  but without success  What did the trick for me was the following  IIS Manager - gt  Sites - gt  MySite - gt  HandlerMappings - gt  aspNetCore - gt  Edit - gt  Request Restrictions - gt  Access - gt  None  it was Script   After that everything worked  even if I replaced the original WebDAV options

User · Answer

I enabled the Failed Request Tracing  and got the following info     lt EventData gt     lt Data Name  ContextId  gt  00000000-0000-0000-0F00-0080000000FA  lt  Data gt     lt Data Name  ModuleName  gt WebDAVModule lt  Data gt     lt Data Name  Notification  gt 16 lt  Data gt     lt Data Name  HttpStatus  gt 405 lt  Data gt     lt Data Name  HttpReason  gt Method Not Allowed lt  Data gt     lt Data Name  HttpSubStatus  gt 0 lt  Data gt     lt Data Name  ErrorCode  gt 0 lt  Data gt     lt Data Name  ConfigExceptionInfo  gt  lt  Data gt    lt  EventData gt    So  I uninstalled the WebDAVModule from my IIS  everything is fine now   The IIS tracing feature is very helpful

User · Answer

Another tip from me  I have used PHP   IIS  and the Handler Mappings for PHP did not have the PUT verb   Go to IIS Manager- Your site- Handler Mappings- PHPxx via FastCGI- Request Restrictions- Verbs  then add PUT   That s it

User · Answer

In my case I had relocated Web Deploy to another port  which was also the IIS port  not 80    I didn t realize at first  but even though there were no errors running both under the same port  seems Web Deploy was most likely responding first instead of IIS for some reason  causing this error  I just moved my IIS binding to another port and all is well

User · Answer

Here is what worked for me   Open up IIS and click on your Site    1 - Double Click on the Modules 2 - Right Click on WebDavPublishing and remove  3 - Restart running WebSite

User · Answer

I had the same issues with PUT  PATCH and DELETE but didn t have anything with WebDav installed  Resolution 1 in this article finally helped me  http   support microsoft com kb 942051

User · Answer

I was using Angular 8 and was  NET core API   I add the following in my service web config file  That resolve my error    lt system webServer gt     lt modules runAllManagedModulesForAllRequests  false  gt       lt remove name  WebDAVModule    gt     lt  modules gt   lt  system webServer gt

User · Answer

Best to just remove the unused WebDAV feature  Go to Programs and Features    Turn Windows Features On or Off and disable WebDAV Publishing under   Internet Information Services    World Wide Web Services    Common HTTP Features

User · Answer

For Windows server 2012 -  Go to Server manager -  Remove Roles and Features -  Server Roles -  Web Server  IIS  -  Web Server -  Common HTTP Features -  Uncheck WebDAV Publishing and remove it -  Restart server

User · Answer

This is my solution  alhamdulillah it worked   Open Notepad as Administrator  Open this file  windir  system32 inetsrv config applicationhost config Press Ctrl-F to find word  quot handlers accessPolicy quot  Add word  quot DELETE quot  after word  quot GET HEAD POST quot   The sentence will become  lt add name  quot PHP via FastCGI quot  path  quot   php quot  verb  quot GET HEAD POST DELETE quot  The word  quot PHP via FastCGI quot  can have alternate word such as  quot PHP via FastCGI1 quot  or  quot PHP via FastCGI2 quot   Save file   Reference  https   docs microsoft com en-US troubleshoot iis http-error-405-website

User · Answer

Taken from here and it worked for me    1 Go to IIS Manager   2 Click on your app   3 Go to  Handler Mappings    4 In the feature list  double click on  WebDAV    5 Click on  Request Restrictions    6 In the tab  Verbs  select  All verbs     7 Press OK

User · Answer

For whatever reason  marking WebDAVModule as  remove  in my web config wasn t enough to fix the problem in my case     I ve found another approach that did solve the problem   If you re in the same boat  try this     In the IIS Manager  select the application that needs to support PUT  In the Features View  find WebDAV Authoring Rules   Double-click it  or select Open Feature from the context menu  right-click   In the Actions pane  find and click on WebDAV Settings     In the WebDAV Settings  find Request Filtering Behavior  and under that  find Allow Verb Filtering   Set Allow Verb Filtering to False  In the Actions pane  click Apply    This prevents WebDAV from rejecting verbs that it doesn t support  thus allowing a PUT to flow through to your RESTful handler unmolested

User · Answer

Another important module that needs reconfiguring before PUT and DELETE will work is the options verb    lt modules gt   lt remove name  WebDAVModule    gt   lt  modules gt   lt handlers gt   lt remove name  OPTIONSVerbHandler    gt   lt remove name  WebDAV    gt   lt add name  OPTIONSVerbHandler  path     verb     modules  ProtocolSupportModule  resourceType  Unspecified  requireAccess  Script    gt   lt  handlers gt    Also see this post  https   stackoverflow com a 22018750 9376681

User · Answer

I tried most of the answers and unfortunately  none of them worked in completion   Here is what worked for me  There are 3 things to do to the site you want PUT for  select the site      Open WebDav Authoring Rules and then select Disable WebDAV option present on the right bar  Select Modules  find the WebDAV Module and remove it  Select HandlerMapping  find the WebDAVHandler and remove it    Restart IIS

[iis] "405 method not allowed" in IIS7.5 for "PUT" method

Examples related to iis

Examples related to iis-7