WCF类型错误和内部服务器错误代码500?

时间:2009-07-01 18:26:06

标签: wcf .net-3.5 iis-6

以下是我的回复信封:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
   <s:Body>
      <s:Fault>
         <faultcode>s:Client</faultcode>
         <faultstring xml:lang="en-US">The creator of this fault did not specify a Reason.</faultstring>
         <detail>
            <ServiceFault xmlns="http://schemas.datacontract.org/2004/07/Zagat.Services.FaultException" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
               <ReasonCollection xmlns:a="http://schemas.datacontract.org/2004/07/Zagat.Enterprise.Domain"/>
               <ReasonMessage>Credentials are not valid</ReasonMessage>
            </ServiceFault>
         </detail>
      </s:Fault>
   </s:Body>
</s:Envelope>
enter code here

这是我的标题:

HTTP/1.1 500 Internal Server Error
Date: Wed, 01 Jul 2009 17:55:33 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 564

如何让IIS返回200而不是500?我的代码在服务器上运行,我只是向客户端发送错误进行处理。

丹尼尔

2 个答案:

答案 0 :(得分:5)

您可以轻松自定义WCF的错误处理。请参阅Nicholas Allen的Indigo博客的Modifying HTTP Error Codes, Part 1Part 2; Andre de Cavaignac WCF: Throwing Exceptions With WebHttpBinding;和Brajendra Singh的Exception Handling in WCF Web Service

答案 1 :(得分:1)

我对SOAP协议的回忆是,故障将作为代码500发送。

错误不是成功回应。它们表明了失败的本质。