asked on

web service 400 bad request with larger amount of data

Ik get a 400 bad request messages when send a large XMLstring to a webservice.
I can send 32K of data just fine, but 64K return the 400 bad request warning.

Below I added a piece of the log. As you can see, it is possible to receive a larger amount of data from the webservice (761024 Bytes works just fine). The 167667 Bytes which is send causes the 400 message.

#Fields: sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken
200 0 0 3062 4249 2
200 0 0 761024 7261 15331
200 0 0 3062 4249 1
200 0 0 5714 7453 12154
200 0 0 3062 4249 2
200 0 0 1414 1373 0
200 0 0 3002 1302 0
200 0 0 7092 6570 1
400 0 0 159 167667 3
200 0 0 3062 4249 3

I have tried adding maxRequestBytes elements to the web.config, but that didn't solve the problem.

Currently this is the webservice part in my web.config

 <system.serviceModel>
  <behaviors>
   <serviceBehaviors>
    <behavior name="ZPPort.IOBehavior">
     <serviceMetadata httpGetEnabled="true" />
     <serviceDebug includeExceptionDetailInFaults="true" />
    </behavior>
   </serviceBehaviors>
  </behaviors>
  <services>
   <service behaviorConfiguration="ZPPort.IOBehavior" name="ZPPort.IO">
    <endpoint address="" binding="wsHttpBinding" contract="ZPPort.IIO">
     <identity>
      <dns value="localhost" />
     </identity>
    </endpoint>
    <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
   </service>
  </services>
 </system.serviceModel>

Open in new window

I run IIS 7.5.

Rovastar

Often the http.sys HTTP handler will capture the 400 http status codes before it reaches IIS.
Have a look also in the http.sys logs anyway.

default location: %windir%\System32\LogFiles\HTTPERR

IS there anything there?
What is the request you are sending? IS this all in the URL? IS it in the headers? Is all the 64K limit under one header?

ASKER CERTIFIED SOLUTION

Rovastar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mattijs33

ASKER

It seems that the wsHttpBinding has a physical limit of 64K, which can't be increased. I have changed the binding and everything works fine.

Mattijs33

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for Mattijs33's comment http:/Q_27290792.html#36483243

for the following reason:

Found own solution.

Rovastar

No it doesn't have a limit of 64KB you can edit it the various parameters under it. That is what I said above.

Here is another link explain it with your 400 error in this.

http://fczaja.blogspot.com/2011/06/wcf-how-to-increase-allowed-request.html

I think it is wrong that your answer is marked correct.....

Rovastar

Mattijs33

ASKER

wsHttpBinding with WS-ReliableMessaging on can't receive more than 64 K per message. You can find more information in this article http://kjellsj.blogspot.com/2007/02/wcf-streaming-upload-files-over-http.html

Rovastar

You question was about wsHttpBinding and I stated that there are limits with that with the exact error you state.

The DEFAULT is 64K for the maxReceivedMessageSize is there for this as in the MS article from the link I had.

http://msdn.microsoft.com/en-us/library/ms731299.aspx

"maxBufferPoolSize

An integer that specifies the maximum buffer pool size for this binding. The default is 524,288 bytes (512 * 1024). Many parts of Windows Communication Foundation (WCF) use buffers. Creating and destroying buffers each time they are used is expensive, and garbage collection for buffers is also expensive. With buffer pools, you can take a buffer from the pool, use it, and return it to the pool once you are done. Thus the overhead in creating and destroying buffers is avoided.

maxReceivedMessageSize

A positive integer that specifies the maximum message size, in bytes, including headers, that can be received on a channel configured with this binding. The sender of a message exceeding this limit will receive a SOAP fault. The receiver drops the message and creates an entry of the event in the trace log. The default is 65536."

Personally i think you are moving the goalposts now with references to something you previously had no mentioned. Streaming with ws-reliable messing is a different case. I am not sure that article is even relevant/factually correct given how old it is, etc.

Mods can a subject matter expert on WCF look over this and make a decision.