尝试使用DELETE谓词时IIS7.5给出500内部服务器错误

时间：2014-02-12 01:40:01

标签： rest iis iis-7.5 http-delete

我正在尝试向IIS7.5资源发出DELETE：

DELETE http://198.252.206.16:48251/Test/foo.ashx HTTP/1.1
Accept: */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E)
Host: 198.252.206.16:48251
Content-Length: 0
Connection: Keep-Alive
Pragma: no-cache

服务器响应：

HTTP/1.1 500 Internal Server Error
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Wed, 12 Feb 2014 01:01:30 GMT
Content-Length: 0

最可怕的是：

  • 它在Cassini（Visual Studio使用的基于.NET的Web服务器）中运行良好
  • Windows事件日志中未记录任何内容
  • 网站的web.config
    • 中的自定义错误已关闭
  • 没有过滤动词（或包含所有动词）
  • 禁用WebDAV模块
  • 未安装LiveStreamingHandler模​​块

为什么IIS不起作用？

重现步骤

使用通用处理程序创建一个网站：

Foo.ashx 

<%@ WebHandler Language="C#" Class="Foo" %>

using System;
using System.Web;

public class Foo : IHttpHandler
{
    public void ProcessRequest(HttpContext context)
    {
    }

    public bool IsReusable { get { return false; } }
}

然后向资源发出DELETE动词。如果您愿意，可以使用Fiddler撰写请求：

enter image description here

你问的其他动词怎么样？

你没有尝试重现它，是吗？好吧，我会在这里向您展示结果：

  • GET ：正常工作
  • POST ：正常工作
  • PUT ：正常工作
  • HEAD ：正常工作
  • TRACE ：501 Not Implemented
  • DELETE ：500 Internal Server Error
  • SEARCH ：405 Method Not Allowed
  • PROPFIND ：500 Internal Server Error
  • PROPPATCH ：500 Internal Server Error
  • PATCH ：405 Method Not Allowed
  • MKCOL ：405 Method Not Allowed
  • COPY ：500 Internal Server Error
  • MOVE ：500 Internal Server Error
  • LOCK ：500 Internal Server Error
  • UNLOCK ：500 Internal Server Error
  • OPTIONS ：200 OK
  • IISUCKSFOO 405 Method Not Allowed

只是为了肛门保持，来自web.config的相关部分的片段：

<?xml version="1.0"?>
<configuration>
    <system.web>
        <httpRuntime/>
        <!-- IISFIX: By default IIS hides errors-->
        <customErrors mode="Off"/>
        <!-- IISFIX: By default IIS ignores the browser's culture -->
        <globalization culture="auto" uiCulture="auto"/>
        <!--Doesn't work for ASP.net web-sites, only ASP.net applications-->
        <trace enabled="true" requestLimit="40" localOnly="false" />

        <compilation debug="true" targetFramework="4.0">
            <assemblies>
                <add assembly="System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            </assemblies>
        </compilation>
    </system.web>

    <!-- ASP.net web-sites do not support WebPageTraceListener (only ASP.net web-applications) 
  So this section doesn't work; and does nothing. 
  But if Microsoft ever fixes IIS, we will start working automagically. -->
    <system.diagnostics>
        <trace>
            <listeners>
                <add name="WebPageTraceListener" type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
            </listeners>
        </trace>
    </system.diagnostics>

    <system.webServer>
        <!-- IISFIX: By default IIS ignores custom error pages -->
        <httpErrors existingResponse="PassThrough"/>
        <defaultDocument>
            <files>
                <clear/>
                <add value="Default.htm"/>
                <add value="Default.asp"/>
                <add value="index.htm"/>
                <add value="index.html"/>
                <add value="iisstart.htm"/>
                <add value="default.aspx"/>
                <add value="test.htm"/>
            </files>
        </defaultDocument>

        <!--IISFIX: By default IIS doesn't understand HTTP protocol-->
        <security>
            <requestFiltering>
                <verbs>
                    <add verb="OPTIONS" allowed="true" />
                    <add verb="GET" allowed="true" />
                    <add verb="HEAD" allowed="true" />
                    <add verb="POST" allowed="true" />
                    <add verb="PUT" allowed="true" />
                    <add verb="TRACE" allowed="true" />
                    <add verb="DELETE" allowed="true" />
                </verbs>
            </requestFiltering>
        </security>

        <modules runAllManagedModulesForAllRequests="true">
            <!--IISFIX: Whatever this is, it causes 405 Method Not Allowed errors on IIS when using PUT. (Microsoft's broken by defult)-->
            <remove name="WebDAVModule"/>
        </modules>

    </system.webServer>
</configuration>

编辑 - 忘记了动词的屏幕截图：

enter image description here

标题中充分询问了这个问题。帖子的其余部分只是填充物，使它看起来像是显示研究工作;这意味着你必须对它进行投票 - upvote arrow上的工具提示是这样说的！

4 个答案:

答案 0 :(得分：8)

答案原来是由微软的默认违约政策引起的。

ASP.net默认决定忽略大多数请求，而不是充当Web服务器，接受请求并处理它们，因为它认为用户不应该这样做。

解决方案是从IIS中删除与ASP.net相关的所有内容，然后重新正确添加：

<强>的web.config 

<?xml version="1.0"?>
<configuration>
    <modules runAllManagedModulesForAllRequests="true">
      <!--IISFIX: Whatever this is, it causes 405 Method Not Allowed errors on IIS when using PUT. (Microsoft's broken by defult)-->
      <remove name="WebDAVModule"/>
    </modules>
    <handlers>
         <!--IISFIX: ASP.net is broken by default. By default they will not accept verbs from the client.
         First we have to rip out everything related to ASP.net-->
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit"/>
      <remove name="ExtensionlessUrlHandler-Integrated-4.0"/>
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit"/>
      <remove name="SimpleHandlerFactory-ISAPI-2.0-64"/>
      <remove name="SimpleHandlerFactory-ISAPI-2.0"/>
      <remove name="SimpleHandlerFactory-Integrated"/>
      <remove name="SimpleHandlerFactory-Integrated-4.0"/>
      <remove name="SimpleHandlerFactory-ISAPI-4.0_64bit"/>
      <remove name="SimpleHandlerFactory-ISAPI-4.0_32bit"/>
         <!-- IISFIX: Now that we're ripped out everything related to ASP.net, put them back correctly.-->
      <add name="SimpleHandlerFactory-ISAPI-4.0_32bit" path="*.ashx" verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness32" responseBufferLimit="0"/>
      <add name="SimpleHandlerFactory-ISAPI-4.0_64bit" path="*.ashx" verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness64" responseBufferLimit="0"/>
      <add name="SimpleHandlerFactory-Integrated-4.0" path="*.ashx" verb="*" type="System.Web.UI.SimpleHandlerFactory" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode,runtimeVersionv4.0"/>
      <add name="SimpleHandlerFactory-Integrated" path="*.ashx" verb="*" type="System.Web.UI.SimpleHandlerFactory" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode"/>
      <add name="SimpleHandlerFactory-ISAPI-2.0" path="*.ashx" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0"/>
      <add name="SimpleHandlerFactory-ISAPI-2.0-64" path="*.ashx" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv2.0,bitness64" responseBufferLimit="0"/>
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" path="*." verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness32" responseBufferLimit="0"/>
      <add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode,runtimeVersionv4.0"/>
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" path="*." verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness64" responseBufferLimit="0"/>

      <!--IISFIX: WebDAV is also buggy, and interferes with client requests-->
      <remove name="WebDAV"/>

    </handlers>
  </system.webServer>
</configuration>

现在的问题是网站无法在其他任何人的机器上运行;现在，web.config中有文件的硬编码路径。

为什么，为什么，微软不能做正确的事情。

完整性

对于我自己的参考，以下是我每次需要添加到web.config的其他内容，因为默认值是错误的：

  <system.web>
    <httpRuntime/>
    <!-- IISFIX: By default IIS hides errors-->
    <customErrors mode="Off"/>
    <!-- IISFIX: By default IIS ignores the browser's culture -->
    <globalization culture="auto" uiCulture="auto"/>
  </system.web>

  <!-- ASP.net web-sites do not support WebPageTraceListener (only ASP.net web-applications) 
  So this section doesn't work; and does nothing. 
  But if Microsoft ever fixes IIS, we will start working automagically. -->
  <system.diagnostics>
    <trace>
      <listeners>
        <add name="WebPageTraceListener" type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
      </listeners>
    </trace>
  </system.diagnostics>

  <system.webServer>
    <!-- IISFIX: By default IIS ignores custom error pages -->
    <httpErrors existingResponse="PassThrough"/>
  </system.webServer>

答案 1 :(得分：2)

我发现在上述解决方案中从处理程序和模块中删除webDav引用仍导致IIS 7.5，IIS 7 Windows Server 2008 r2（我从未测试过IIS 8）的http方法PUT，DELETE

HTTP错误500.21 - 内部服务器错误 Handler＆＃34; ExtensionlessUrlHandler-Integrated-4.0＆＃34;有一个糟糕的模块＆＃34; ManagedPipelineHandler＆＃34;

此服务器错误具有误导性，并且还提供了缺少处理程序的不正确.net安装，并且可以通过重新安装.Net来修复，但如果它只影响PUT或者它可能不是解决方案DELETE请求到无扩展路由处理程序（GET，POST和OPTIONS很好）。我读了很多关于在MVC和Web api中启用put和delete方法的帖子，似乎声称这是一个修复因此我无论如何都尝试了几次，重新启动IIS等，没有改变错误。

问题并没有消失，直到我添加了runManagedModulesForWebDavRequests =＆＃34; true＆＃34;属性为modules元素。

＆LT; modules runAllManagedModulesForAllRequests =＆＃34; true＆＃34; runManagedModulesForWebDavRequests =＆＃34;真＆＃34; ＆GT;

http://www.iis.net/configreference/system.webserver/modules

默认情况下，runManagedModulesForWebDavRequests =＆＃34; false＆＃34;这意味着任何webDav请求都被路由到WebDav。就我可以推断，就IIS而言，webdav请求都是http PUT或DELETE请求，即使您已从web配置中删除了webdav处理程序，并且您的请求主体也不符合webdav请求。卸载webDav可能也可以解决问题，但我从未尝试过;我有其他站点在依赖它的同一台服务器上运行。

答案 2 :(得分：1)

我在这里找到了答案：

ASP.NET Core with IIS - HTTP Verb Not Allowed

这是web.config 

<configuration>
<!-- To customize the asp.net core module uncomment and edit the following section. 
     For more info see https://go.microsoft.com/fwlink/?linkid=838655 -->
<system.webServer>
    <modules>
        <remove name="WebDAVModule" />
    </modules>
    <handlers>
        <remove name="aspNetCore" />
        <remove name="WebDAV" />
        <!-- I removed the following handlers too, but these
             can probably be ignored for most installations -->
        <remove name="ExtensionlessUrlHandler-Integrated-4.0" />
        <remove name="OPTIONSVerbHandler" />
        <remove name="TRACEVerbHandler" />

        <add name="aspNetCore" 
             path="*" 
             verb="*" 
             modules="AspNetCoreModule" 
             resourceType="Unspecified" />
    </handlers>
    <aspNetCore processPath="%LAUNCHER_PATH%" 
                arguments="%LAUNCHER_ARGS%" 
                stdoutLogEnabled="false"
                stdoutLogFile=".\logs\stdout" />
</system.webServer>

答案 3 :(得分：0)

将来需要注意的是，当您将代码部署到非本地的任何内容时，您可以将可能的硬编码凭据更改为通用访问帐户。我有一整天的确切问题，看到与DELETE一起使用的LDAP .net请求使用前雇员的硬编码员工ID作为{{1} }。它工作正常，直到他的ID最终从我们的系统中删除然后一切都变坏了。在一天半之后，我们再次找到用于测试目的的硬编码凭证。举例说明不同测试环境中必须考虑的不同事项。

相关问题
最新问题