"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:

 <add name="ResultHandler" path="*.cab" verb="PUT" type="FileUploadApplication.ResultHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode" />

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.

Davide Icardi · Answer 1 · 2016-11-17T08:46:03.897

232

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:

<system.webServer>
    <modules>
        <remove name="WebDAVModule" />
    </modules>
    <handlers>
        <remove name="WebDAV" />
    </handlers>
</system.webServer>

edited Nov 17 '16 at 08:46

answered Feb 20 '13 at 09:57

Davide Icardi

10,707
7
51
67

4

Using the following MS article, I added the remove tag to handlers, but it still did not work. Thanks to your answer I see I also needed to add it to the modules section. Much appreciated. Here is the article: http://www.asp.net/web-api/overview/testing-and-debugging/troubleshooting-http-405-errors-after-publishing-web-api-applications – Tod Birdsall Mar 17 '15 at 14:28
Great, you saved me hours of painful debugging! :) – Kaspars Ozols Dec 01 '16 at 14:00
Simple and easy fix, Thanks! – MorenajeRD Jan 25 '18 at 16:56
I've tried that but doesn't work for me. I'm still getting the error 405 - Method not allowed. Note that I'm using IIS Express and the error somehow only occurs on PUT but works for GET, POST AND DELETE. – Thierry Jul 15 '19 at 21:33

score 51 · Accepted Answer · answered Jun 03 '11 at 06:35

51

I enabled the Failed Request Tracing, and got the following info:

 <EventData>
  <Data Name="ContextId">{00000000-0000-0000-0F00-0080000000FA}</Data>
  <Data Name="ModuleName">WebDAVModule</Data>
  <Data Name="Notification">16</Data>
  <Data Name="HttpStatus">405</Data>
  <Data Name="HttpReason">Method Not Allowed</Data>
  <Data Name="HttpSubStatus">0</Data>
  <Data Name="ErrorCode">0</Data>
  <Data Name="ConfigExceptionInfo"></Data>
 </EventData>

So, I uninstalled the WebDAVModule from my IIS, everything is fine now~

The IIS tracing feature is very helpful.

answered Jun 03 '11 at 06:35

smwikipedia

52,824
76
267
432

2

Thanks for your answer ! After 2 days of research, the only working solution I found to avoid "405 Method Not Allowed" was to define the CORS headers in the `Application_BeginRequest` method, as mentioned in this answer http://stackoverflow.com/a/14631068/827168. But your answer is better than all other because it helps spot the problem instead of applying some random patch :) – pomeh Oct 15 '14 at 08:54
@pomeh I always believe in making the logic complete. :) – smwikipedia Sep 09 '15 at 03:12
1

@Demodave Check here:https://technet.microsoft.com/en-us/library/cc731223%28v=ws.10%29.aspx – smwikipedia Nov 26 '15 at 01:59
1

Note, you should also go into the Handler Mappings and delete WebDAV from there, or else you'll get the error message `Handler "WebDAV" has a bad module "WebDAVModule" in its module list`. – pipedreambomb Apr 11 '17 at 14:31

score 26 · Answer 3 · answered Aug 27 '12 at 21:27

26

I had this problem with WebDAV when hosting a MVC4 WebApi Project. I got around it by adding this line to the web.config:

<handlers>
  <remove name="WebDAV" />
  <add name="WebDAV" path="*" verb="*" modules="WebDAVModule"
      resourceType="Unspecified" requireAccess="None" />
</handlers>

As explained here: http://evolutionarydeveloper.blogspot.co.uk/2012/07/method-not-allowed-405-on-iis7-website.html

answered Aug 27 '12 at 21:27

Nick

5,765
5
39
59

Best solution for someone who actually needs WebDAV. Whether anyone needs WebDAV is a separate discussion. – MrBoJangles Feb 26 '18 at 18:23

score 26 · Answer 4 · answered Apr 02 '15 at 14:14

26

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.

answered Apr 02 '15 at 14:14

coding_idiot

12,860
9
56
111

This Works! Don't know if all 3 steps can be done by editing web.config file, but this made it easy using only the IIS Management Console. Just note that there are 3 HandlerMapping entries starting with WebDAV* - I removed all 3 and life was good. – SlimsGhost Jun 03 '15 at 02:26
2

I tried uninstalling WebDav and didn't work. Then I followed all three steps above and `PUT` started working. – rareyesdev Nov 05 '15 at 04:37
1

Steps 2 and 3 can be applied to a virtual directory without affecting the rest of the site. – Tonatio Apr 10 '18 at 13:17
Step 1 was already "done" on my IIS. I followed steps 2 and 3, and it worked like a charm! Thank you! – Helvio Oct 23 '18 at 18:10
1

Thanks a lot. you saved me. After 7 hours frustration, tried all answer that i could and finally your answer hit me. :) – Zeeshan Safdar Oct 09 '19 at 08:02
1

Thanks, this is it. – Ahmad Hamdy Jul 06 '20 at 08:30

score 26 · Answer 5 · edited May 23 '17 at 12:03

26

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.

edited May 23 '17 at 12:03

Community

1
1

answered Sep 23 '15 at 08:55

goran85

443
5
19

3

This helped me, but I'll clarify with my experience. 2. (Web Service) app. 3. double click the Handler Mappings icon in the center panel. – Gary Feb 24 '17 at 00:20

score 19 · Answer 6 · answered May 12 '17 at 21:26

19

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

answered May 12 '17 at 21:26

SliverNinja - MSFT

29,007
10
98
161

Thanks ! This totally fixed my issue! – wmehanna May 31 '17 at 17:47

score 18 · Answer 7 · answered Jun 27 '13 at 12:32

18

Removing the WebDAV-module should be sufficient. Just change your Web.config:

<system.webServer>
    <modules runAllManagedModulesForAllRequests="true">
        <remove name="WebDAVModule" />

answered Jun 27 '13 at 12:32

Dunken

7,909
4
51
76

score 8 · Answer 8 · answered Dec 08 '19 at 13:27

I was using Angular 8 and was .NET core API. I add the following in my service web.config file. That resolve my error.

<system.webServer>
  <modules runAllManagedModulesForAllRequests="false">
    <remove name="WebDAVModule" />
  </modules>
</system.webServer>

score 7 · Answer 9 · answered Jan 24 '19 at 17:42

7

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.

answered Jan 24 '19 at 17:42

nPcomp

5,621
1
37
45

score 5 · Answer 10 · answered Jul 04 '18 at 11:39

Another important module that needs reconfiguring before PUT and DELETE will work is the options verb

<modules>
<remove name="WebDAVModule" />
</modules>
<handlers>
<remove name="OPTIONSVerbHandler" />
<remove name="WebDAV" />
<add name="OPTIONSVerbHandler" path="*" verb="*" modules="ProtocolSupportModule" resourceType="Unspecified" requireAccess="Script" />
</handlers>

Also see this post: https://stackoverflow.com/a/22018750/9376681

score 5 · Answer 11 · answered Jul 22 '20 at 12:00

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="*" both on the site and on the server itself, but without success.

What did the trick for me was the following:

IIS Manager -> Sites -> MySite -> HandlerMappings -> aspNetCore -> Edit

-> Request Restrictions -> Access -> None (it was Script).

After that everything worked, even if I replaced the original WebDAV options.

Confirmed with .NET 3.0 Blazor deploy to IIS – Eric Bourque Feb 13 '21 at 14:03 — Eric Bourque, Feb 13 '21 at 14:03

score 4 · Answer 12 · answered Dec 11 '13 at 18:09

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.

score 4 · Answer 13 · answered Mar 14 '18 at 11:53

4

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!

answered Mar 14 '18 at 11:53

Stefan Pintilie

467
4
5

1

This is the answer php users need. – SpeedOfRound Mar 29 '18 at 13:52

score 3 · Answer 14 · answered Jul 27 '13 at 13:12

3

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

answered Jul 27 '13 at 13:12

gust1n

123
2
7

score 2 · Answer 15 · 2014-08-23T14:49:55.457

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.

score 2 · Answer 16 · answered Apr 04 '16 at 21:19

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.

score 2 · Answer 17 · answered Jun 25 '18 at 09:43

2

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.

answered Jun 25 '18 at 09:43

Savan Gadhiya

814
1
10
11

score 1 · Answer 18 · answered Jan 31 '21 at 02:45

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 "handlers accessPolicy"
Add word "DELETE" after word "GET,HEAD,POST".
The sentence will become <add name="PHP_via_FastCGI" path="*.php" verb="GET,HEAD,POST,DELETE"
The word "PHP_via_FastCGI" can have alternate word such as "PHP_via_FastCGI1" or "PHP_via_FastCGI2".
Save file.

Reference: https://docs.microsoft.com/en-US/troubleshoot/iis/http-error-405-website

Arjun Mukherji · Answer 19 · 2015-07-31T22:37:54.203

If IIS app pool is running under classic mode, make sure you have the following in your web.config

<remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" />

    <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" />

score 0 · Answer 20 · answered May 06 '16 at 21:56

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. ;)

score 0 · Answer 21 · answered May 31 '18 at 12:32

To prevent WebDav from getting enabled at all, remove the following entry from the ApplicationHost.config: <add name="WebDAVModule" />

The entry is located in the modules section.

Exact location of the config: C:\Windows\System32\inetsrv\config\applicationHost.config

score 0 · Answer 22 · answered Apr 19 '21 at 07:00

0

for asp.net core 5

IIS-> Sites -> MySite -> HandlerMappings -> aspNetCore -> Request Restrictions -> Access -> None (it was Script).

answered Apr 19 '21 at 07:00

Loyola Edwin

1

"405 method not allowed" in IIS7.5 for "PUT" method

22 Answers22

Linked