6249Re: [soaplite] Upgraded client, getting SOAP errors
- Oct 14, 2008
> I tried changing the SOAP version to 1.1 just to send the content-You can change the content-type with
> type that it's expecting, but then other issues come up, like a
> hardcoded prefix SOAP-ENC:Array needs to be soapenc:Array.
> Can I force the content-type of a v1.2 transaction to text/xml?
> What else can be done to remedy this situation? The people who own
> the remote server will certainly not upgrade because of this.
$soap->transport->http_request->header('Content-type' => 'text/xml');
- << Previous post in topic Next post in topic >>