texas-bronius

Ok, I see this SOAP response was actually MOTM/multipart, and much to my chagrin, NuSOAP does not actually support multipart. That was a really long and round-about way of discovering that :( For posterity, ended up parsing the raw response with string parse for known cases, like: $response = $client->response; $error = $client->getError(); if ($error) { if ($error === 'XML error parsing SOAP payload on line 1: Not well-formed (invalid token)') { dpm($response, 'OK: multipart response to be parsed');...

Not hundred percent what the thing was.. but was able to set headers and get success: Content-Type: text/xml; charset=UTF-8 Accept-Encoding: gzip, deflate from $client->soap_defencoding = 'UTF-8'; $client->setHTTPEncoding('gzip, deflate'); respectively. I'm still getting XML error parsing SOAP payload on line 1: Not well-formed (invalid token). but that seems to be coming from the server. Initial response is an http 200 with a good-looking SOAP message of 200 and OK within. /shrug

So what I'm doing.. When I dump my curl request raw from php app via $client->request and paste it into SoapUI and run it there, the request goes thru perfectly. But it's not running in my php app! I keep getting an IIS 400 Bad Request (not a SOAP error). The differences I see in the raw http request from my nuSoap php app and SoapUI with the exact same payload are: POST /Action.svc in app is POST https://example.com/Action.svc (absolute, FQD) in SoapUI Accept-Encoding: gzip,deflate in SoapUI, not...

Hmm.. an update. While that xml declaration did cause my request to fail with an IIS 400 Bad Request, changing the encoding to UTF-8 allows the raw request to go through (when copy/pasted into SoapUI) but not via my php app. I think it's got to do with the http request now..

I am outputting my client SOAP request to screen and copy/pasting into SoapUI: When run like this, I get a 400: Bad Client Request from the SOAP service, but when I remove the XML declaration in the first bit: <?xml version="1.0" encoding="ISO-8859-1"?> so that the next bit is the rest of the standard SOAP request, the request goes through, and I get a 200 OK in a proper SOAP response. What is it about the xml declaration that's breaking my request, how can I remove it before the request is sent,...