Hi Barry,
yes, let me explain our issue in more detail.
We have deployed a SOAP service on the GW and if we send a valid (syntactically correct) request to it (e.g. via SoapUI) we get a valid response from the application. But if we modify this request (e.g. insert/remove a character in one of the tags, so the opening tag and the closing tag are not identical anymore, meaning the request is syntactically wrong), we get the mentioned HTTP-, instead of a SOAP-response.
Ok, the content of the 400 error code also mentions this "The request sent by the client was syntactically incorrect.", but when handling with SOAP-requests you also would expect SOAP-responses. Otherwise you might be pointed in the wrong direction in case of troubleshooting. Maybe also the Client is not able to correctly handle HTTP-responses.
If we send the same wrongly modified request directly to the application we see for example the following response:
com.ctc.wstx.exc.WstxParsingException: Unexpected close tag </typ:Authentication>; expected </typ:Password>. at [row,col {unknown-source}]: [6,26]
That's why I'm wondering if this behavior can somehow be changed.
I hope it's much clearer now.
Thank you!
Ciao Stefan