禁用ASP.NET MVC WebAPI的WebDAVModule会产生哪些副作用？
Hey there! Since you've already fixed the 405 Method Not Allowed issue by removing the WebDAV module and handler from your web.config, let's break down the potential impacts of this change—especially since you don't directly depend on WebDAV:
No disruption to core Web API functionality
WebDAV is an optional, standalone module designed for file management over HTTP (like moving, locking, or editing server files). It has no overlap with core Web API features such as RESTful routing, model binding, or controller actions. Disabling it won't break your existing API endpoints or their normal behavior.Permanent resolution of HTTP verb conflicts
The 405 error you encountered happened because WebDAV intercepts verbs likePUTandDELETEby default—even when your API uses them for non-file-related operations. Removing the module ensures these verbs reach your Web API controllers as intended, which was exactly the fix you needed.No missing features (since you don't use WebDAV)
If your app never required exposing file system access via WebDAV (e.g., letting clients upload or modify files through WebDAV protocols), you won't notice any missing functionality. This is the case for most standard Web APIs focused on data exchange rather than file storage.Tiny, harmless performance boost
Disabling an unused module means one less component loading and processing requests. The performance improvement is minimal, but it's a positive side effect with no downsides.Rare edge case: Dependencies in other modules
It's extremely unlikely, but if any third-party or custom modules in your app rely on hooks or functionality from WebDAVModule, you might see unexpected behavior. However, since you stated you don't directly depend on WebDAV, this scenario is almost non-existent.
Final Takeaway
Since you don't use WebDAV features, disabling the module is a safe, low-risk change that only fixes your 405 issue without introducing new problems.
内容的提问来源于stack exchange，提问作者Teoman shipahi
