0

We have an implementation where we call an external matching web service. When the records that i send are many, i get the following error: System.CalloutExceptionLine 429The following exception has occurred: Web service callout failed: Unexpected element. Parser was expecting element 'http://schemas.xmlsoap.org/soap/envelope/:Envelope' but found ':html'

I have checked that the xml from Salesforce is the whole file that should be sent (not cut). However, when the file reaches apache, it is already cut. What could be the problem? Is there a threshold limit?

4
  • 1
    What is the length of an outbound request? Can you post the message here?
    – kurunve
    Commented Jul 13, 2020 at 7:16
  • Hi kurunve, you mean the length of the XML file ? If yes, it is 1,24 MB (1.301.777 byte) Commented Jul 13, 2020 at 8:33
  • What are you using to create the SOAP callout? Is it based on WSDL2Apex, or did you hand craft the XML payload? Commented Jul 14, 2020 at 3:26
  • Hi Daniel. it is based on WSDL2Apex. Probably it was the Web Application Firewall that was cutting the XML file! Problem seems to be solved! Commented Jul 14, 2020 at 13:13

1 Answer 1

0

Finally issue seems to be solved. It was because of the Web Application Firewall that was cutting the XML File!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .