I've imported a WSDL file and have used the resulting SOAP classes to create an app that communicates with a remote service. It was easy to setup and worked liked a charm, for small amounts of data (around 80 items). However, when I send an object with more items, I get the following error: Request Entity Too Large (413). I've been told the server has been modified to accept larger entities and I've been asked to change settings on the client side to also allow for this.

I've imported a WSDL file and have used the resulting SOAP classes to create an app that communicates with a remote service. It was easy to setup and worked liked a charm, for small amounts of data (around 80 items). However, when I send an object with more items, I get the following error: Request Entity Too Large (413). I've been told the server has been modified to accept larger entities and I've been asked to change settings on the client side to also allow for this.

Specifically:
maxBufferPoolSize="2147483647"
maxReceivedMessageSize="2147483647"
readerQuotas
maxDepth="32"
maxStringContentLength="2147483647"
maxArrayLength="2147483647"
maxBytesPerRead="4096"
maxNameTableCharCount="16384"

I'm not sure where to find these settings though - the instruction is coming from a C# developer. I'm using Delphi Tokyo 10.2.3 and have looked at Soap.SOAPHTTPClient, Soap.SOAPHTTPTrans and WinAPI.WinInet to see if there are any properties like this but cannot find the equivalent in these units.

Can anyone point me in the right direction? Does anyone know where to set these limits?

Comments

  1. I do not think it is on the client side which is your application. When i worked with WSDL any type of configuration issue was on the server side.

    Request from the server what they allow to be sent to them. Also check on your side what exactly you are sending on the request.

    Look at this link to see if it helps.

    craftcms.stackexchange.com - 413 “Request Entity Too Large” error with uploading a file

    ReplyDelete
  2. Richard Baroniunas Thanks Richard, you were right. It is apparently fixed on the server side... so no changes required on my side.

    ReplyDelete

Post a Comment