I'm dealing with an issue of large messages generating quota exceeded errors. The default value for maxStringContentLength, for example, is only 8K and the maxReceivedMessageSize limit is 64K. In order for my service to function correctly, I've had to increase these values considerably.
I've also tried setting each to 0 as a way of indicating there should be no limit constraint. This has not worked.
I'm also observing that message size is much greater when I use wsHttpBinding versus basicHttpBinding.
I'd appreciate any comments or suggestions about these issues. TIA

maxReceivedMessageSize and maxStringContentLength
anilpatel32
You have to provide explicit values for max message, string, array (etc) size, and you should attempt to limit which endpoints (contracts) require large messages so that you can throttle other calls and reduce your exposure to DoS attacks.
WSHttpBinding by default uses message security, which increases message size. BasicHttpBInding does not have security enabled by default. Thus, smaller payload.
Also, be careful when hosting in IIS, since there are also message size contraints in ASP.NET <processModel> config.
WL_07
please give me more details