What is the difference between a request in curl and in SoapUI?
Hi.
I currently try to connect to a production endpoint throguh SoapUI, but when I try the server generates the following exception:
SAXParseException: The markup in the document preceding the root element must be well-formed.
This have had me stumped for some time (I am sure the XML is correct, other users have no problem with the same WSDL).
But then I tried the same request through curl, and the whole process went smoothly without problems.
I have used curl to setup the same header settings in both requests, but still curl is the only way working. As I need to set up a test project, SoapUI is the preferred way to run these requests. What is the difference between SoapUI and curl (when doing requests)?
Here is the request:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:vmo="...">
<soapenv:Header>
<wsse: Security soapenv:mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-31860110"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>...</wsse:Username>
<wsse: Password
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">...</wsse: Password>
</wsse:UsernameToken>
</wsse: Security>
</soapenv:Header>
<soapenv:Body>
<vmo:CheckStatusRequest>
<vmo:Voucher>
<vmo:ActivationCode>323456789012</vmo:ActivationCode>
</vmo:Voucher>
</vmo:CheckStatusRequest>
</soapenv:Body>
</soapenv:Envelope>
I have removed some sensitive information, but the requests is as above. And the four spaces you might notice is just there to not have smileys in my question :)
As I said, I have used curl to ensure that the http headers are the same, as they are presented as raw data in SoapUI. Any hint would be welcome. Also, the endpoint is behind https, if that makes any difference.
Best regards.
