Large WCF web service request failing with 400 HTTP Bad Request

Question

I ve encountered this apparently common problem and have been unable to resolve it   If I call my WCF web service with a relatively small number of items in an array parameter  I ve tested up to 50   everything is fine   However if I call the web service with 500 items  I get the Bad Request error   Interestingly  I ve run Wireshark on the server and it appears that the request isn t even hitting the server - the 400 error is being generated on the client side   The exception is   System ServiceModel ProtocolException  The remote server returned an unexpected response   400  Bad Request  --- gt  System Net WebException  The remote server returned an error   400  Bad Request    The system serviceModel section of my client config file is    lt system serviceModel gt       lt bindings gt           lt wsHttpBinding gt               lt binding name  WSHttpBinding IMyService  closeTimeout  00 01 00                  openTimeout  00 01 00  receiveTimeout  00 10 00  sendTimeout  00 01 00                  bypassProxyOnLocal  false  transactionFlow  false  hostNameComparisonMode  StrongWildcard                  maxBufferPoolSize  524288  maxReceivedMessageSize  2147483647                  messageEncoding  Text  textEncoding  utf-8  useDefaultWebProxy  true                  allowCookies  false  gt                   lt readerQuotas maxDepth  32  maxStringContentLength  8192  maxArrayLength  2147483647                      maxBytesPerRead  4096  maxNameTableCharCount  16384    gt                   lt reliableSession ordered  true  inactivityTimeout  00 10 00                      enabled  false    gt                   lt security mode  None  gt                       lt transport clientCredentialType  Windows  proxyCredentialType  None                          realm      gt                       lt message clientCredentialType  Windows  negotiateServiceCredential  true                          establishSecurityContext  true    gt                   lt  security gt               lt  binding gt           lt  wsHttpBinding gt       lt  bindings gt       lt client gt           lt endpoint address  http   serviceserver MyService svc              binding  wsHttpBinding  bindingConfiguration  WSHttpBinding IMyService              contract  SmsSendingService IMyService  name  WSHttpBinding IMyService    gt       lt  client gt   lt  system serviceModel gt    On the server side  my web config file has the following system serviceModel section    lt system serviceModel gt       lt services gt           lt service name  MyService MyService  behaviorConfiguration  MyService MyServiceBehaviour   gt               lt endpoint address    binding  wsHttpBinding  bindingConfiguration  MyService MyServiceBinding  contract  MyService IMyService  gt               lt  endpoint gt               lt endpoint address  mex  binding  mexHttpBinding  contract  IMetadataExchange   gt           lt  service gt       lt  services gt       lt bindings gt         lt wsHttpBinding gt           lt binding name  MyService MyServiceBinding  gt             lt security mode  None  gt  lt  security gt           lt  binding gt         lt  wsHttpBinding gt       lt  bindings gt       lt behaviors gt           lt serviceBehaviors gt               lt behavior name  MyService MyServiceBehaviour  gt                   lt  -- To avoid disclosing metadata information  set the value below to false and remove the metadata endpoint above before deployment -- gt                   lt serviceMetadata httpGetEnabled  true   gt                   lt  -- 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 -- gt                   lt serviceDebug includeExceptionDetailInFaults  true   gt               lt  behavior gt           lt  serviceBehaviors gt       lt  behaviors gt   lt  system serviceModel gt    I ve looked at a fairly large number of answers to this question with no success   Can anyone help me with this

User · Answer

In my case  it was not working even after trying all solutions and setting all limits to max  In last I found out that a Microsoft IIS filtering module Url Scan 3 1 was installed on IIS website  which have it s own limit to reject incoming requests based on content size and return  404 Not found page    It s limit can be updated in  windir  System32 inetsrv urlscan UrlScan ini file by setting MaxAllowedContentLength to the required value   For eg  following will allow upto 300 mb requests  MaxAllowedContentLength 314572800  Hope it will help someone

User · Answer

I found the answer to the Bad Request 400 problem   It was the default server binding setting  You would need to add to server and client default setting   binding name    openTimeout  00 10 00  closeTimeout  00 10 00  receiveTimeout  00 10 00  sendTimeout  00 10 00  maxReceivedMessageSize  2147483647  maxBufferPoolSize  2147483647  maxBufferSize  2147483647

User · Answer

It might be useful to debug the client  turn off Tools Options Debugging General  Enable Just My Code   click Debug Exceptions  catch all first-chance exceptions  for managed CLR exceptions  and see if there is an exception under-the-hood on the client before the protocol exception and before the message hits the wire    My guess would be some kind of serialization failure

User · Answer

For what it is worth  an additional consideration when using  NET 4 0 is that if a valid endpoint is not found in your configuration  a default endpoint will be automatically created and used   The default endpoint will use all default values so if you think you have a valid service configuration with a large value for maxReceivedMessageSize etc   but there is something wrong with the configuration  you would still get the 400 Bad Request since a default endpoint would be created and used   This is done silently so it is hard to detect  You will see messages to this effect  e g   No Endpoint found for Service  creating Default Endpoint  or similar  if you turn on tracing on the server but there is no other indication  to my knowledge

User · Answer

In the server in  NET 4 0 in web config you also need to change in the default binding  Set the follwowing 3 parms       lt  basicHttpBinding gt        lt   --http   www intertech com Blog post NET-40-WCF-Default-Bindings aspx       - Enable transfer of large strings with maxBufferSize  maxReceivedMessageSize and maxStringContentLength     -- gt        lt  binding   maxBufferSize  2147483647  maxReceivedMessageSize  2147483647    gt           lt  readerQuotas   maxStringContentLength  2147483647     gt                  lt   binding gt

User · Answer

Try setting maxReceivedMessageSize on the server too  e g  to 4MB        lt binding name  MyService MyServiceBinding              maxReceivedMessageSize  4194304  gt    The main reason the default  65535 I believe  is so low is to reduce the risk of Denial of Service  DoS  attacks   You need to set it bigger than the maximum request size on the server  and the  maximum response size on the client   If you re in an Intranet environment  the risk of DoS attacks is probably low  so it s probably safe to use a value much higher than you expect to need   By the way a couple of tips for troubleshooting problems connecting to WCF services    Enable tracing on the server as described in this MSDN article  Use an HTTP debugging tool such as Fiddler on the client to inspect the HTTP traffic

User · Answer

You can also turn on WCF logging for more information about the original error  This helped me solve this problem   Add the following to your web config  it saves the log to C  log Traces svclog   lt system diagnostics gt       lt sources gt           lt source name  System ServiceModel                    switchValue  Information  ActivityTracing                    propagateActivity  true  gt               lt listeners gt                   lt add name  traceListener                       type  System Diagnostics XmlWriterTraceListener                       initializeData   c  log Traces svclog    gt               lt  listeners gt           lt  source gt       lt  sources gt   lt  system diagnostics gt

User · Answer

Just want to point out  Apart from MaxRecivedMessageSize  there are also attributes under ReaderQuotas  you might hit number of items limit instead of size limit  MSDN link is here

User · Answer

I was also getting this issue also however none of the above worked for me as I was using a custom binding  for BinaryXML  after an long time digging I found the answer here  -  Sending large XML from Silverlight to WCF  As am using a customBinding  the maxReceivedMessageSize has to be set on the httpTransport element under the binding element in the web config    lt httpsTransport maxReceivedMessageSize  4194304    gt

[c#] Large WCF web service request failing with (400) HTTP Bad Request

Examples related to c#

Examples related to .net

Examples related to wcf

Examples related to web-services