The size of the messages that can be received on the wire by services using the BasicHttpBinding is bounded by the amount of memory allocated for each message. This bound on message size is intended to limit exposure to DoS-style attacks.

There is also a MaxBufferSize property on the BasicHttpBinding:

• For buffered transports, (TransferMode set to Buffered). This value is always equal to that specified by the MaxReceivedMessageSize.

• For streamed transports (TransferMode set to Streamed), only the SOAP headers must be buffered to generate the message. The body can be streamed in on-demand. In this case, MaxBufferSize is less than or equal to MaxReceivedMessageSize, where MaxReceivedMessageSize bounds the size of the overall message (headers and body) and MaxBufferSize bounds the size of the SOAP headers.

The following example sets MaxReceivedMessageSize to 1,000,000 bytes.

            BasicHttpBinding binding = new BasicHttpBinding();
            // Use double the default value
            binding.MaxReceivedMessageSize = 65536 * 2;

The value of this property can also be set in the configuration file.

<configuration>
  <system.serviceModel>

    <bindings>
      <basicHttpBinding>
        <binding name="Binding1"
                 maxReceivedMessageSize = "1000000">
          <security mode="None" />
        </binding>
      </basicHttpBinding>
    </bindings>

  </system.serviceModel>

</configuration>

• Full trust for the immediate caller. This member cannot be used by partially trusted code. For more information, see Using Libraries from Partially Trusted Code.

Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows CE, Windows Mobile for Smartphone, Windows Mobile for Pocket PC

.NET Framework

.NET Compact Framework

Reference