Thanks for the reply.
So, you say that I can configure client independently, without the need to
configure the server? The problem is when downloading data, never with
upload. And how can I do this? Because I used this client config:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="ServiceSoap" closeTimeout="00:01:00" openTimeout="00:01:00"
receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false"
bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
maxBufferSize="65536" maxBufferPoolSize="524288"
maxReceivedMessageSize="65536"
messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
useDefaultWebProxy="true">
<readerQuotas maxDepth="32" maxStringContentLength="8192"
maxArrayLength="16384"
maxBytesPerRead="4096" maxNameTableCharCount="16384" />
<security mode="None">
<transport clientCredentialType="None" proxyCredentialType="None"
realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
</binding>
</basicHttpBinding>
</bindings>
<client>
<endpoint address="http://servidor:8080/ws/Service.asmx"
binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_IOrderServi ce"
contract="IOrderService"
behaviorConfiguration="LargeQuotaBehavior"
name="ServiceSoap" />
</client>
</system.serviceModel>
</configuration>
and I get this error:
"There is no endpoint behavior named 'LargeQuotaBehavior'. "
Thanks in advance.
"Marc Gravell" <ma**********@gmail.comescreveu na mensagem
news:uN**************@TK2MSFTNGP03.phx.gbl...
Are you sure that is your web.config? WCF typically has a LOT more config
than that (in system.ServiceModel), for either the client or the server.
If your app is setting up the configuration through code (which is
entirely possible with WCF) then you need to find the bit of code that
configures the binding. Note that these quotas don't just apply to the
server; setting it at the server is useful for uploading larger arrays
etc, but the quotas may need to be independently set at the client if the
problem is the server *returning* too much data.
Marc