HTTP PUT not allowed in ASP.NET Web API

Question

On my Web API project, I cannot perform an HTTP PUT to my resources. I've read through some similar questions on this problem and I've followed the recommended advice.

First off, I uninstalled WebDAV completely on my machine (Windows 7 64-bit) and subsequently rebooted my machine.

Secondly, the WebDAV handlers were specified as removed in my web.config and the HTTP PUT verb was specified as being allowed for the Extensionless URL Handler.

<modules runAllManagedModulesForAllRequests="false">   <remove name="WebDAVModule"/> </modules>  <handlers>   <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />   <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" />   <remove name="ExtensionlessUrlHandler-Integrated-4.0" />   <remove name="WebDAV"/>   <add name="ExtensionlessUrlHandler-Integrated-4.0"        path="*."        verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS"        type="System.Web.Handlers.TransferRequestHandler"        resourceType="Unspecified"        requireAccess="Script"        preCondition="integratedMode,runtimeVersionv4.0" />   <add name="AttributeRouting" path="routes.axd" verb="*" type="AttributeRouting.Web.Logging.LogRoutesHandler, AttributeRouting.Web" /> </handlers> 

I even tried adding the ISAPI Extensionless URL Handler (32-bit and 64-bit) and changing my application from the integrated pipeline App Pool to the classic App Pool.

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

I'm currently using Thinktecture IdentityModel to enable Cross Origin Resource Sharing (CORS) support. For my sanity, I've gone with the nuclear option of enabling everything to make sure the HTTP PUT is actually allowed.

config.RegisterGlobal(httpConfig);  config.ForAllResources()       .ForAllOrigins()       .AllowAllMethods()       .AllowAllRequestHeaders(); 

The Attribute Routing NuGet package is configured to pick up all routes from the current assembly and any subtypes of ApiController.

config.AddRoutesFromAssembly(Assembly.GetExecutingAssembly()); config.AddRoutesFromControllersOfType<ApiController>(); 

My resource has the PUT attribute properly specified as well.

[PUT("/API/Authenticate/Link/{key}/{identifier}")] public Boolean LinkUser(Guid key, String identifier) { ... } 

Every resource I look up on this matter recommends the same exact thing: Uninstalling WebDAV, disabling the WebDAV handlers and making sure that the Extensionless URL handler is properly configured. I've done all that and it still doesn't work.

In fiddler, I'm getting the following:

PUT https://localhost/Test/API/Authenticate/Link/Foo/Bar  {"Message":"The requested resource does not support http method 'PUT'."} 

What am I doing wrong?

Answer 1

Apparently, there is a known problem within AttributeRouting wherein the HttpPut methods are currently non-functional in ASP.NET Web API.

The currently accepted workaround is add the appropriate verb onto the route until a proper fix comes along:

Web API RC sealed a vital interface for route detection by the underlying framework. Though the interface is now public, the change won't be released until vNext. So here are some workarounds:

• Use AR attributes in combination with HttpGet, HttpPost, HttpPut, or HttpDelete attributes from System.Web.Http:

[GET("some/url"), HttpGet] public string Method1() {}  [PUT("some/url"), HttpPut] public string Method2() {}  [POST("some/url"), HttpPost] public string Method3() {}  [DELETE("some/url"), HttpDelete] public string Method4() {} 

Answer 2

Double check that you're using [HttpPut] from System.Web.Http.

Under some circumstances you can end up using the attribute from System.Web.Mvc.

This was resulting in 405s for us.