reference
http://stackoverflow.com/questions/19959273/still-getting-413-request-entity-too-large-even-after-setting-the-web-config
I found the solution looking in another web.config example
This was my web.config:
http://stackoverflow.com/questions/19959273/still-getting-413-request-entity-too-large-even-after-setting-the-web-config
I found the solution looking in another web.config example
This was my web.config:
<binding name="basicHttpsBinding" maxReceivedMessageSize="524288000" />
<binding name="mexHttpBinding" maxReceivedMessageSize="524288000" />
</basicHttpBinding>
</bindings>
<service behaviorConfiguration="ServicioCCMasAvalBehavior" name="ServicioCCMasAval.ServicioCCMasAval">
<endpoint address="/" binding="basicHttpBinding" contract="ServicioCCMasAval.IServicioCCMasAval" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>
</services>
I was missing the bindingConfiguration on the enpoint. Now this is my working webconfig:
<binding name="basicHttpBinding" maxReceivedMessageSize="524288000" />
<binding name="mexHttpBinding" maxReceivedMessageSize="524288000" />
</basicHttpBinding>
</bindings>
<service behaviorConfiguration="ServicioCCMasAvalBehavior" name="ServicioCCMasAval.ServicioCCMasAval">
<endpoint address="/" binding="basicHttpBinding" bindingConfiguration="basicHttpBinding" contract="ServicioCCMasAval.IServicioCCMasAval" />
</service>
</services>
No comments:
Post a Comment