maxReceivedMessageSize and maxBufferSize in app.config

Question

How to increase maxReceivedMessageSize and maxBufferSize parameters in app.config file to 2000000 before running the application.

score 66 · Accepted Answer · answered Feb 21 '13 at 10:24

66

You need to do that on your binding, but you'll need to do it on both Client and Server. Something like:

<system.serviceModel>
    <bindings>
        <basicHttpBinding>
            <binding maxBufferSize="64000000" maxReceivedMessageSize="64000000" />
        </basicHttpBinding>
    </bindings>
</system.serviceModel>

answered Feb 21 '13 at 10:24

Mathew Thompson

55,877
15
127
148

Thanks @mattytommo,this is what i wanted. – Vishal I P Feb 21 '13 at 12:47
Thank you! It works for me as well. It works even when I provide this change for client only. – Sergey Sep 24 '14 at 11:04
perfect, you saved me a lot of time :) ++1 – Dan Dinu Oct 09 '14 at 19:29
1

I don't get why this answer has so many upvotes. It is wrong, you are not required to set those values on both the client and the server. See my answer below. – D.R. Nov 22 '16 at 14:35
Your little bold words are life-saving. Thanks! – kerbasaurus May 24 '17 at 18:01

score 16 · Answer 2 · edited Sep 25 '14 at 22:46

16

You can do that in your app.config. like that:

maxReceivedMessageSize="2147483647"

(The max value is Int32.MaxValue )

Or in Code:

WSHttpBinding binding = new WSHttpBinding();
binding.Name = "MyBinding";
binding.MaxReceivedMessageSize = Int32.MaxValue;

Note:

If your service is open to the Wide world, think about security when you increase this value.

edited Sep 25 '14 at 22:46

abatishchev

98,240
88
296
433

answered Feb 21 '13 at 10:44

Jacob

751
1
6
18

I don't have app.config file, where i can create it? – Brayan Loayza Mar 19 '21 at 17:40

D.R. · Answer 3 · 2019-12-18T12:58:35.020

15

The currently accepted answer is incorrect. It is NOT required to set maxBufferSize and maxReceivedMessageSize on the client and the server binding. It depends!

If your request is too large (i.e., method parameters of the service operation are memory intensive) set the properties on the server-side, if the response is too large (i.e., the method return value of the service operation is memory intensive) set the values on the client-side.

For the difference between maxBufferSize and maxReceivedMessageSize see MaxBufferSize property?.

edited Dec 18 '19 at 12:58

answered Mar 07 '16 at 15:05

D.R.

20,268
21
102
205

I'm not sure why we have to bother to set the limits at all. What if I don't know how large a payload's going to be (think cardinalities of 0..n)? – René Schindhelm Mar 20 '19 at 17:23
You should always have a protection against "too large". Otherwise you're wide open to DoS attacks. – D.R. Mar 21 '19 at 07:22
Safety aside (which really shouldn't be neglected for public facing services), you won't know at compile-time the amount of data you might send or retrieve from a service call (think object graphs f.e.). You can only estimate. I think [Large Data and Streaming](https://learn.microsoft.com/en-us/dotnet/framework/wcf/feature-details/large-data-and-streaming) is of interest, especially the chapter "Special Security Considerations for Large Data". – René Schindhelm Apr 10 '19 at 20:13

score 2 · Answer 4 · answered Dec 12 '17 at 15:35

2

If you are using a custom binding, you can set the values like this:

<customBinding>
    <binding name="x">
        <httpsTransport maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" />
    </binding>
</customBinding>

answered Dec 12 '17 at 15:35

rox

71
2
11

Brijesh Kumar Tripathi · Answer 5 · 2018-01-15T13:28:16.150

Open app.config on client side and add maxBufferSize and maxReceivedMessageSize attributes if it is not available

Original

  <system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="Service1Soap"/>
      </basicHttpBinding>
    </bindings>

After Edit/Update

  <system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="Service1Soap" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"/>
      </basicHttpBinding>
    </bindings>

score 0 · Answer 6 · answered Jun 18 '14 at 07:04

0

Easy solution: Check if it works for you..

Goto web.config

Find binding used by client.

change as,

maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"

Done.

answered Jun 18 '14 at 07:04

Aki

149
4
13

score 0 · Answer 7 · edited Jun 22 '18 at 12:07

0

binding name="BindingName" 
maxReceivedMessageSize="2097152" 
maxBufferSize="2097152" 
maxBufferPoolSize="2097152"

on client side and server side

edited Jun 22 '18 at 12:07

H. Pauwelyn

13,575
26
81
144

answered Jul 23 '15 at 08:57

Sunita Badsra

1

maxReceivedMessageSize and maxBufferSize in app.config

7 Answers7

Linked