The only time we notice this value appears to be when the service crashes because the value is too low. The quick way to fix this is to set it to some very large number. Then no problem. What I was wondering about is are there any negative consiquences to setting this value high? I can see that it can potentially give some protection f...
I'm getting the maxreceivedmessagesize error for messages greater than 64K. The problem is that I've already changed everything in both server and client, and it's not fixing the problem. here's my web.config on the server and then the silverlight client config: <system.serviceModel> <bindings> <basicHttpBinding> <binding ...
What is the fundamental difference between the two? On the server side on the service, I am using readerQuotas to accomodate large string lengths (Int32.MaxValue). What is the significance of maxReceivedMessagesize then? ...
Searched with no luck... I keep getting The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. It makes sense, so I go into both Server and client config and make the change: Client <system.serviceModel> ...
My WCF Service has an OperationContract that accepts, as a parameter, an array of objects. This can potentially be quite large. After looking for fixes for Bad Request: 400, I found the real reason: the maximum message size. I know this question has been asked before in MANY places. I've tried what everyone says: "Increase the sizes ...