405 Message, method not allowed with Web Api

Question

I have got the following on an API controller:

public void UpdateClient(Client client)
    {
        try
        {
            if (ModelState.IsValid)
            {
                db.Entry(client).State = EntityState.Modified;
                db.SaveChanges();
            }
        }
        catch
        {
            throw new HttpResponseException(new HttpResponseMessage(HttpStatusCode.NotFound));
        }
    }

And the following on the page:

$.ajax({
            url: "api/client/UpdateClient",
            type: "PUT",
            contentType: 'json',
            data: ko.toJSON(model.selectedClient()),
            success: function (result) {
                getClients();
                $("#loader").hide();
            },
            failure: function (result) {
                alert(result.d);
                $("#loader").hide();
            },
            error: function (XMLHttpRequest, textStatus, errorThrown) {
                alert("An error occurred, please try again.");
                $("#loader").hide();
            }
        });

But this gives the error 405 Method Not Allowed, can anyone see where I may have gone wrong? For reference the url for the api is ok as I use the same api controller for other functions too.

Also the selectedClient() is a Client object received via WebApi so should match perfectly to PUT up again.

Which webserver are you using? Because in IIS you have to manually enable Put and Delete see forums.iis.net/t/1166025.aspx — nemesv
– nemesv, Commented Oct 9, 2012 at 19:55
Then see the How do I enable verbs like PUT/DELETE for my web application? from the IIS Express FAQ. — nemesv
– nemesv, Commented Oct 9, 2012 at 20:13
Which verbs do I change on the host file though, there's quite a few — user1166905
– user1166905, Commented Oct 9, 2012 at 20:24

Salman · Accepted Answer · 2012-11-29 07:17:14Z

23

If you are using IIS7 and have WebDav installed, try removing it. I was getting the same error only with the PUT verb and it solved the issue

Update: You can read about WebDav here: http://www.iis.net/learn/get-started/whats-new-in-iis-7/what39s-new-for-webdav-and-iis-7

answered Nov 29, 2012 at 7:17

Salman

3,2274 gold badges27 silver badges33 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Vipul Over a year ago

+1, It solved my problem, but what if we want to have that module also?

Salman Over a year ago

Try adding the following in your web.config file code<system.webServer> <modules runAllManagedModulesForAllRequests="true"> <remove name="WebDAVModule" /> </modules> </system.webServer>

Sven Over a year ago

In my case I also had to add <handlers><remove name="WebDAV" /></handlers> to the system.webServer section (I'm on IIS8).

Amit Kumar Ghosh Over a year ago

or one might disable WebDAV publishing from Control Panel.

Maggie Ying · Accepted Answer · 2012-10-09 21:02:35Z

5

Do you have [HttpPut] attribute on your UpdateClient action? Also, do you have a route that takes in the {action} as the routeTemplate? For example:

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

One more thing, try 'application/json' for the content-type in your ajax code instead of 'json'.

edited Oct 9, 2012 at 21:02

answered Oct 9, 2012 at 20:45

Maggie Ying

10.2k2 gold badges37 silver badges37 bronze badges

Comments

user1166905 · Accepted Answer · 2012-10-09 20:44:27Z

2

Looks like these two lines were wrong, I changed them as follows:

contentType: 'application/json',
data: "{client: " + ko.toJSON(model.selectedClient()) + "}",

And now goes in.

answered Oct 9, 2012 at 20:44

user1166905

2,6327 gold badges47 silver badges76 bronze badges

Comments

JSideris · Accepted Answer · 2015-08-20 23:49:10Z

1

Note to future troubleshooters: I got this error when my "Put" controller was unintentionally expecting an additional parameter that wasn't being used.

answered Aug 20, 2015 at 23:49

JSideris

5,3114 gold badges36 silver badges54 bronze badges

Comments

Austin Salgat · Accepted Answer · 2015-11-10 15:40:04Z

0

My issue was that under project properties, I was using Local IIS instead of IIS Express, and it defaulted to port 80 which blocked DELETE requests. Changing to IIS Express fixed it.

answered Nov 10, 2015 at 15:40

Austin Salgat

4155 silver badges14 bronze badges

Collectives™ on Stack Overflow

405 Message, method not allowed with Web Api

5 Answers 5

4 Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

4 Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related