WebAPI Delete not working - 405 Method Not Allowed

Question

I appreciate any help on this as the site is supposed to go live tonight!

I have a web api controller with a Delete method. The method executes fine on my local machine running IIS Express (Windows 8) but as soon as I deployed it to the live IIS server (Windows Server 2008 R2) it stopped working and throws the following error message:

HTTP Error 405.0 - Method Not Allowed The page you are looking for cannot be displayed because an invalid method (HTTP Verb) is being used

I have looked around the web for solutions and I implemented most reasonable ones. My web config has the following settings:

<system.webServer>
    <validation validateIntegratedModeConfiguration="false" />
<handlers>
    <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
    <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" />
    <remove name="ExtensionlessUrlHandler-Integrated-4.0" />
    <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" />
    <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" />
    <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" />
</handlers>
</system.webServer>

I have also tried to change the Handler Mappings and Request Filtering in IIS to no avail. Please note that the WebDAV Authoring Rules in IIS seems to be disabled.

Any ideas will be greatly appreciated Thanks.

score 205 · Accepted Answer · edited Dec 20 '13 at 20:37

205

I found the solution eventually! If you come across the same issue, add the following to your web.config

<system.webServer>
    <validation validateIntegratedModeConfiguration="false"/>
    <modules runAllManagedModulesForAllRequests="true">
        <remove name="WebDAVModule"/> <!-- ADD THIS -->
    </modules>
    ... rest of settings here

I hope this helps

edited Dec 20 '13 at 20:37

Leniel Maccaferri

94,281
40
348
451

answered Mar 25 '13 at 16:05

Chris

4,757
3
17
24

2

I also had to add a remove in the handlers section as per http://stackoverflow.com/a/6698096/254156 – rrrr Dec 06 '13 at 14:22
3

Also worked here. But can someone explain me the relation to WebDAVModule? – Boas Enkler Dec 13 '13 at 09:19
11

for those who just copy-paste: runAllManagedModulesForAllRequests="true" is not really needed and can actually break other things. – Zar Shardan Jan 16 '14 at 08:11
Some other web posts will suggest removing the module using IIS Modules section, this disables it but it still causes this/a similar problem, this is the most reliable method – Anthony Main Jul 30 '14 at 09:52
Thanks for your answer, but unfortunately it didn't worked for me (I'm using IIS 7.5). 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 – pomeh Oct 15 '14 at 08:51
5

@ZarShardan (and others) FYI: If you remove the runAllManagedModulesForAllRequests="true" attribute you will also need to add under the node as well. – Aaron Mar 09 '15 at 16:48
You can also perform this operation from ISS manager (Modules and then Handlers - remove WebDAV). – Gerino Apr 07 '16 at 09:50

score 68 · Answer 2 · edited May 23 '17 at 12:02

68

In some cases removing it just from modules can produce next error:

500.21 Handler "WebDAV" has a bad module "WebDAVModule" in its module list

Module: IIS Web Core Notification: ExecuteRequestHandler"

solution was suggested here. Also need to remove it from handlers.

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

edited May 23 '17 at 12:02

Community

1
1

answered Sep 22 '14 at 12:58

aleha

7,140
2
34
41

1

this is works for me, but can someone shed some light on what is WebDAV actually? – Nazrul Muhaimin Jan 16 '19 at 07:40

Hugo Nava Kopp · Answer 3 · 2017-06-19T10:38:19.127

In my case none of the above solutions was working. This was because I had changed the name of the parameter in my Delete method.

I had

public void Delete(string Questionid)

instead of

public void Delete(string id)

I need to use the id name because that's the name that is declared in my WebApiConfig file. Note the id name in the third and fourth lines:

            config.Routes.MapHttpRoute(
            name: "DefaultApi",
            routeTemplate: "api/{controller}/{id}",
            defaults: new { id = RouteParameter.Optional }
        );

I got this solution from here.

score 15 · Answer 4 · edited May 23 '16 at 21:18

15

The Javascript for HTTP DELETE verb must be like this:

$.ajax({
    **url: "/api/SomeController/" + id,**
    type: "DELETE",
    dataType: "json",
    success: function(data, statusText) {
        alert(data);
    },
    error: function(request, textStatus, error) {
        alert(error);
        debugger;
    }
});

Do not use something like this:

...
data: {id:id}
...

as when you use the POST method.

edited May 23 '16 at 21:18

Michael Gaskill

7,567
10
37
39

answered Apr 16 '15 at 07:54

Pavel Kharibin

755
2
16
23

1

Hi @Pavel, this is correct if you're indeed using a fully RESTful implementation. Unfortunately, not everyone does this and it's quite common to see developers using POST instead of DELETE etc. Thanks for clarifying this. – Chris Apr 16 '15 at 08:34

score 5 · Answer 5 · answered Dec 20 '17 at 13:51

After trying almost every solutions here this worked for me. Add this in your APIs config file

<system.webServer>
    <handlers>
      <remove name="WebDAV" />
      <remove name="ExtensionlessUrlHandler-Integrated-4.0" />
      <remove name="OPTIONSVerbHandler" />
      <remove name="TRACEVerbHandler" />
      <add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" />
    </handlers>
    <modules>
        <remove name="WebDAVModule" />
    </modules>
</system.webServer>

Tried lots of things, this worked. .NET version 4.6.1 - Thanks. — Ketan, Jul 03 '20 at 05:08

score 5 · Answer 6 · answered Mar 20 '20 at 10:10

5

If you are using IIS 7.0 or later version. This issue is mainly related to WebDAV extension module on IIS server. this happened while Using Post OR delete action.

Please try below setting in web config

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

answered Mar 20 '20 at 10:10

Abhishek B.

4,886
14
47
85

1

omg it worked for me. after 6 hours later i found the solution. thx a lot!! – Ender Kaya Nov 30 '20 at 19:25
1

good to hear it fixed.. @EnderKaya – Abhishek B. Dec 01 '20 at 12:13

score 3 · Answer 7 · edited May 20 '15 at 02:45

I also had the same problem, I am calling WebAPi and is getting this error. Adding following configuration in web.config for services solved my problem

    <modules runAllManagedModulesForAllRequests="true">
        <remove name="WebDAVModule"/> <!-- add this -->
    </modules>

in web.config file solved my problem. This is How i was calling from client side

using (var client = new HttpClient())
{
    client.BaseAddress = new Uri(environment.ServiceUrl);
    client.DefaultRequestHeaders.Accept.Clear();
    client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
    HttpResponseMessage response = client.DeleteAsync("api/Producer/" + _nopProducerId).Result;
    if (response.IsSuccessStatusCode)
    {
        string strResult = response.Content.ReadAsAsync<string>().Result;
    }
}

score 2 · Answer 8 · answered Jan 08 '16 at 11:59

2

Go to applicationHost.config (usually under C:\Windows\System32\inetsrv\config) file and comment out the following line in applicationHost.config

1)Under <handlers>:

<add name="WebDAV" path="*" verb="PROPFIND,PROPPATCH,MKCOL,PUT,COPY,DELETE,MOVE,LOCK,UNLOCK" modules="WebDAVModule" resourceType="Unspecified" requireAccess="None" />

2)Also comment out the following module being referred by the above handler under <modules>

<add name="WebDAVModule" />

answered Jan 08 '16 at 11:59

arviman

4,587
37
44

Or use the other answer https://stackoverflow.com/a/47907578/1754743 to REMOVE these handlers in your own web.config, if you don't want to (or can't) modify the machine-wide config file – Ekus May 29 '19 at 15:00

score 2 · Answer 9 · answered Apr 05 '19 at 06:10

2

In my case, I missed to add {id} to the [Route("")] and I got the same error. Adding that fixed the problem for me: [Route("{id}")]

answered Apr 05 '19 at 06:10

Reza

548
7
14

So many hours of wasted time, and if it wasn't for you i still couldn't solve this.... I'm wonder why it doesn't return 404 :@ – deadManN Aug 26 '19 at 08:20

score 1 · Answer 10 · answered Mar 24 '16 at 12:19

I had 405 error Method Not Allowed because I had omitted to make the Delete method on the WebApi controller public.

It took me a long time to find this (too long!) because I would have expected a Not Found error in this case, so I was incorrectly assuming that my Delete method was being denied.

The reason for Not Allowed rather than Not Found is that I also had a Get method for the same route (which will be the normal case when implementing REST). The public Get function is matched by the routing and then denied because of the wrong http method.

A simple error I know but it may save someone else some time.

score 1 · Answer 11 · answered Apr 24 '16 at 09:42

Just to add. If this is your config

config.Routes.MapHttpRoute(
            name: "DefaultApi",
            routeTemplate: "api/{controller}/{id}",
            defaults: new { id = RouteParameter.Optional }

please keep doing as Hugo said, and do not set Route attribute to the controller get method, this gave a problem in my case.

score 0 · Answer 12 · answered Jun 20 '16 at 12:24

I had the similar issue but for PUT - none of the other suggestions worked for me.

However i was using int rather than the default string for the id. adding {id:int} to the route solved my problem.

    [Route("api/Project/{id:int}")]
    public async Task<IHttpActionResult> Put(int id, [FromBody]EditProjectCommand value)
    {
       ...
    }

score 0 · Answer 13 · answered Mar 31 '17 at 20:47

We had to add custom headers to our web.config as our request had multiple headers that confused the API response.

<httpProtocol>
    <customHeaders>
        <remove name="Access-Control-Allow-Methods" />
        <remove name="Access-Control-Allow-Origin" />
        <remove name="Access-Control-Allow-Headers" />
    </customHeaders>
</httpProtocol>

score -1 · Answer 14 · answered Jan 26 '15 at 07:54

-1

[HttpPost] attribute on the top of Delete method solved this issue for me:

[HttpPost]
public void Delete(int Id)
{
  //Delete logic
}

answered Jan 26 '15 at 07:54

Andrey Gubal

3,397
2
16
21

That could be a reason why it's working for you. I was on an earlier version, circa early 2013, so quite a few things have been fixed since. Glad to know it's working for you though. – Chris Jan 26 '15 at 20:54
4

This isn't a good answer to be honest. The people whose problem was resolved using this are using POST instead of DELETE so it couldn't and shouldn't work – Alexander Derck Jul 10 '17 at 11:40
I believe this is because you are using `data` (i.e. the body of the request) instead of `params` (i.e. the url of the request) in the client side. – Thomas Sauvajon Jul 17 '17 at 15:29
I agree with Alexander Derck, this is a kludge rather than a solution. – Basem Sayej Nov 20 '17 at 03:36

WebAPI Delete not working - 405 Method Not Allowed

14 Answers14

Linked