“远程服务器返回意外响应：（400）错误请求”
Posted
技术标签:
【中文标题】“远程服务器返回意外响应：（400）错误请求”【英文标题】："The remote server returned an unexpected response: (400) Bad Request" 【发布时间】：2013-08-22 13:34:16 【问题描述】：我现在完全被这个问题难住了。过去 2 天我一直在阅读各种文章和博客，并进行了大部分建议的更改，但我仍然遇到这个问题。
基本上，我将一个数组对象作为参数从客户端传递给服务，然后出现上述错误。
我可以处理 200 条记录，但如果我将其设置为 250，例如，它会返回 400 错误。 我已经启用了跟踪等，但是当它出错时根本没有记录任何内容。客户端和服务都在同一环境中运行（测试目的）-windows 2008r2 我将展示两个配置文件以及我如何调用服务。
客户端配置
<?xml version="1.0"?>
<!--
For more information on how to configure your ASP.NET application, please visit
http://go.microsoft.com/fwlink/?LinkId=169433
-->
<configuration>
<configSections>
</configSections>
<system.web>
<compilation debug="true" targetFramework="4.0"/>
<httpRuntime executionTimeout="180" maxRequestLength="2147483647" />
</system.web>
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding name="WSHttpBinding_FinHqclient" closeTimeout="00:25:00"
openTimeout="00:25:00" receiveTimeout="10:50:00" sendTimeout="00:25:00"
maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647"
useDefaultWebProxy="true" allowCookies="false">
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"
maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
<security>
<transport realm="" />
</security>
</binding>
</wsHttpBinding>
<basicHttpBinding>
<binding maxBufferPoolSize="2147483647" name="test" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" >
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"
maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
</binding>
</basicHttpBinding>
</bindings>
<behaviors>
<endpointBehaviors>
<behavior name="maxItemsInObjectGraphBehaviour">
<dataContractSerializer maxItemsInObjectGraph="2147483646" />
</behavior>
</endpointBehaviors>
</behaviors>
<client>
<endpoint address="http://server:8123/service.svc" behaviorConfiguration="maxItemsInObjectGraphBehaviour"
binding="wsHttpBinding" bindingConfiguration="WSHttpBinding_FinHqclient"
contract="sfgServ.FinHqclient" name="WSHttpBinding_FinHqclient">
<identity>
<servicePrincipalName value="host/local" />
</identity>
</endpoint>
</client>
</system.serviceModel>
</configuration>
这是服务器配置文件：
<?xml version="1.0"?>
<configuration>
<configSections>
<section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />
</configSections>
<system.diagnostics>
<sources>
<source name="System.ServiceModel"
switchValue="Information, ActivityTracing"
propagateActivity="true">
<listeners>
<add name="traceListener"
type="System.Diagnostics.XmlWriterTraceListener"
initializeData= "c:\log\Traces.svclog" />
</listeners>
</source>
</sources>
</system.diagnostics>
<system.web>
<compilation debug="true" targetFramework="4.0" />
<httpRuntime executionTimeout="180" maxRequestLength="2147483647" />
</system.web>
<system.serviceModel>
<diagnostics>
<messageLogging logEntireMessage="true" logMalformedMessages="true"
logMessagesAtServiceLevel="true" logMessagesAtTransportLevel="true" />
</diagnostics>
<protocolMapping>
<add scheme="http" binding="wsHttpBinding"/>
</protocolMapping>
<services>
<service name="SFG.CRM2011.WebServiceFinHqFinHq.Service" behaviorConfiguration="SFG.CRM2011.WebServiceFinHq.ServiceBehavior">
<endpoint address="" binding="wsHttpBinding" bindingConfiguration="SFG.CRM2011.WebServiceFinHq.BindConfig"
contract="sfgServ.IClientFinHQ" behaviorConfiguration="SFG.CRM2011.WebServiceFinHq.wsServiceEndpointBehavior">
</endpoint>
<endpoint contract="IMetadataExchange" binding="mexHttpBinding" bindingConfiguration="higherMessageSize_MEX" address="mex" />
</service>
</services>
<behaviors>
<endpointBehaviors>
<behavior name="SFG.CRM2011.WebServiceFinHq.wsServiceEndpointBehavior">
<dataContractSerializer maxItemsInObjectGraph="2147483646" />
</behavior>
</endpointBehaviors>
<serviceBehaviors>
<behavior name="SFG.CRM2011.WebServiceFinHq.ServiceBehavior">
<serviceMetadata httpGetEnabled="true" policyVersion="Policy15" />
<serviceDebug includeExceptionDetailInFaults="true"/>
<dataContractSerializer maxItemsInObjectGraph="2147483647"/>
</behavior>
<behavior >
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<serviceMetadata httpGetEnabled="true" policyVersion="Policy15"/>
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="true"/>
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
<bindings>
<wsHttpBinding >
<binding name="SFG.CRM2011.WebServiceFinHq.BindConfig" maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" >
<security mode="None">
<transport clientCredentialType="None" />
<message establishSecurityContext="false" />
</security>
<reliableSession enabled="true" ordered="True" inactivityTimeout="00:10:00" />
<readerQuotas maxDepth="2147483647"
maxStringContentLength="2147483647"
maxArrayLength="2147483647"
maxBytesPerRead="2147483647"
maxNameTableCharCount="2147483647" />
</binding>
</wsHttpBinding>
<mexHttpBinding>
<binding name="higherMessageSize_MEX" />
</mexHttpBinding>
<basicHttpBinding >
<binding maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" >
<readerQuotas maxStringContentLength="2147483647" />
</binding>
</basicHttpBinding>
</bindings>
</system.serviceModel>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="9000000" />
</requestFiltering>
</security>
</system.webServer>
</configuration>
以下是我如何在客户端调用此服务...
List<FUMStruct> fList = new List<FUMStruct>();
for (int i = 0; i < 250; i++)
var t = new FUMStruct();
t.clientID = "1234";
t.ClientCRMGUID = new Guid("9EACA7AE-FE7E-E211-956A-00505622E202");
t.CRMAccountCRMGUID = new Guid("A63D9ADC-0CFF-E211-94E9-00505622E202");
t.Balance = 200 + i;
fList.Add(t);
var serv = new FinHqclientClient();
serv.UpdateLastFUMGUID(fList.ToArray());
【问题讨论】：
Large WCF web service request failing with (400) HTTP Bad Request 的可能重复项 不，我以前看过那篇文章，我在那里尝试了这个建议（从我的配置文件可以看出），但没有成功 对不起！我显然没有详细讨论。 【参考方案1】：这是因为绑定中有一个“名称”值。因此，我们设置的自定义值没有被应用，它正在加载服务器默认值（甚至不确定不同绑定的“默认值”保存在哪里！）我在网上阅读的一篇文章中发现了这一点并制作了一个新的仅使用基本绑定的服务..一直失败，直到我删除了名称然后它才开始工作！ 然后我必须弄清楚如何为 wsHttpBinding 执行此操作，因为使用该绑定，如果您不指定名称（然后显然您无法引用配置），您会遇到各种或安全问题等，并且服务不起作用..所以解决方案是添加另一个没有 name 属性的绑定。
最后只需要在服务器端进行设置，因为我保留了默认客户端值（低于上面示例中的值）并且它仍然有效。下面是完整的 web.config..注意我必须默认 basicHttpbinding 和 wsHttpbinding
<bindings>
<wsHttpBinding >
<binding ***name="problemWithValue"*** maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" >
<security mode="None">
<transport clientCredentialType="None" />
<message establishSecurityContext="false" />
</security>
<reliableSession enabled="true" ordered="True" inactivityTimeout="00:10:00" />
<readerQuotas maxDepth="2147483647"
maxStringContentLength="2147483647"
maxArrayLength="2147483647"
maxBytesPerRead="2147483647"
maxNameTableCharCount="2147483647" />
</binding>
<binding maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" >
<security mode="None">
<transport clientCredentialType="None" />
<message establishSecurityContext="false" />
</security>
<reliableSession enabled="true" ordered="True" inactivityTimeout="00:10:00" />
<readerQuotas maxDepth="2147483647"
maxStringContentLength="2147483647"
maxArrayLength="2147483647"
maxBytesPerRead="2147483647"
maxNameTableCharCount="2147483647" />
</binding>
</wsHttpBinding>
<mexHttpBinding>
<binding name="higherMessageSize_MEX" />
</mexHttpBinding>
<basicHttpBinding >
<binding maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" >
<readerQuotas maxStringContentLength="2147483647" />
</binding>
</basicHttpBinding>
</bindings>
【讨论】：
【参考方案2】：我注意到您增加了客户端的 maxRequestLength，但没有增加服务器：
<system.web>
<!-- ... -->
<httpRuntime executionTimeout="180" maxRequestLength="2147483647" />
</system.web>
此配置选项实际上只与服务器相关，因为它设置了入站请求的允许大小。无论如何，我会将此部分添加到您的服务器配置文件中，看看是否可以解决问题。默认请求大小为 4MB，根据经验我知道这可能会导致您报告的错误。
【讨论】：
谢谢，试过了，但还是不行。仍然收到相同的错误消息。好奇怪！以上是关于“远程服务器返回意外响应：（400）错误请求”的主要内容，如果未能解决你的问题，请参考以下文章