Incomplete webservice request

I'm trying to get a webservice call out of the Mx cloud to a published webservice (containing a Base64 string) on premise. but it fails every time with a general error pop-up to contact the networkadmin. When looking into the logging (in browser) the created SOAP body is incomplete and goes off screen. This apparently is not just a visual issue as the downloaded log shows the body of the request cut short at the exact same point (982 chars in the logline). When the same webservice is called from a local computer the call succeeds and generates proper and complete logging. It looks like a chunking issue. Other webservices show that long Base64 strings are logged in chunks of 72 chars, whilst the faulty one generates a line of 982 chars without closing tags. How come the exact same webservice works from a local computer and fails from the cloud?
0 answers