.netcore PUT method 405 Method Not Allowed

Question

I have a simple model as that has 2 fields and with the following put method, i'm tring to update it in the db. Everymethod including delete works, however put method always returns a 405 error in Postman. (tried WebDAV solutions as well.) What am I missing here?

PUT METHOD:

{
    "MasterId":1,
    "MasterName":"Test"
}

Action

[HttpPut("{id:int}")]
public async Task<IActionResult> PutMaster(int id, Master master)
{
    if (id != master.MasterId)
    {
        return BadRequest();
    }

    //...some code
    return NoContent();
}

First observation is that the called URL does not match the route template of the controller action. — Nkosi, Nov 24 '19 at 11:12

score 12 · Answer 1 · answered Nov 24 '19 at 11:22

12

If you are using IIS to run your application and have WebDav module, that can be an issue. For some strange reason WebDav does not allow PUT.

I just uninstalled it, and it helped.

answered Nov 24 '19 at 11:22

Ilya Chernomordik

27,817
27
121
207

5

If you don't want to uninstall WebDav, you can also exclude the module by adding a web.config to the folder of the application. Add the following section to it: ` ` – Peter Eysermans Aug 31 '20 at 14:33
Thank you! I would have never figured this out on my own! – Nick Henry Apr 08 '21 at 13:33

score 7 · Answer 2 · answered Dec 28 '21 at 19:53

7

If your application is being hosted under IIS, running API in ASP.NET Core, include this line in the Web.Config file

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

answered Dec 28 '21 at 19:53

César Augusto

593
1
7
7

I had the same problem after publishing on host(plesk). with this solution my issue fixed. – Ghadir Farzaneh Mar 07 '22 at 09:58
For IIS, it is the correct solution – vidgarga Mar 07 '22 at 15:00

Shahar Shokrani · Accepted Answer · 2019-11-24T11:58:44.183

6

Using the [HttpPut("{id:int}")] route attribute, you will need to refer your api with: http://localhost:5000/api/masters/{id}

In your exmample:

PUT http://localhost:5000/api/masters/1

So the id in the param also not needed:

[HttpPut("{id:int}")] 
public async Task<IActionResult> PutMaster(Master master)

And it is a bad practice to expose entity framework object to the client, you should use a DTO class and map it to the entity framework object.

edited Nov 24 '19 at 11:58

answered Nov 24 '19 at 11:14

Shahar Shokrani

7,598
9
48
91

Why is it a bad idea to use EF model there? – Sin5k4 Nov 24 '19 at 11:26
2

DTO is good practice to minimize traffic, controlling serialization, security, separation of concerns etc... see this https://stackoverflow.com/a/5910546/6844481 – Shahar Shokrani Nov 24 '19 at 11:29

Nkosi · Answer 4 · 2019-11-24T11:22:47.180

First observation is that the called URL

api/masters

does not match the route template of the controller action [HttpPut("{id:int}")] which would map to a URL like

api/masters/{id:int}

Call the correct URL that matches the action's route template

PUT api/masters/1

The error itself is because most likely you have another route that matches the provided URL but not the HTTP Verb. like a root [HttpGet] on one of the controller actions. This explains why you get a 405 Method Not Allowed error and not a 404 Not Found error

score 1 · Answer 5 · answered Nov 24 '19 at 11:15

1

Your method should be

 [HttpPut("{id:int}")]
        public async Task<IActionResult> PutMaster(int id,[FromBody]  Master master)
{}

You need to add [FromBody] attribute in the method.

Request url should be

PUT api/masters/1

answered Nov 24 '19 at 11:15

MesutAtasoy

772
2
13
24

.netcore PUT method 405 Method Not Allowed

5 Answers5

Linked