CopyPastor

Detecting plagiarism made easy.

Score: 1; Reported for: Exact paragraph match Open both answers

Possible Plagiarism

Plagiarized on 2023-09-18
by Jiayao

Original Post

Original - Posted on 2013-12-18
by Hugo



            
Present in both answers; Present only in the new answer; Present only in the old answer;

You may try using the following binding configuration to solve the problem:
<bindings> <basicHttpBinding> <binding maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text"> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> </binding> </basicHttpBinding> </bindings>
Besides, this case shows another way to solve the exception. [Azure Cloud Service "The remote server returned an error: (413) Request Entity Too Large."][1]
Hope it helps.
[1]: https://stackoverflow.com/questions/25235908/azure-cloud-service-the-remote-server-returned-an-error-413-request-entity-t
For the record
I think I got it. The Web.Config from the service does not have the binding information. I placed this info in it, and voila!
<bindings> <basicHttpBinding> <binding maxBufferPoolSize="2147483647" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text"> <readerQuotas maxDepth="2000000" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /> </binding> </basicHttpBinding> </bindings>
Note here that the binding did not have a name specified.

        
Present in both answers; Present only in the new answer; Present only in the old answer;