Loading ...
Sorry, an error occurred while loading the content.

6249Re: [soaplite] Upgraded client, getting SOAP errors

Expand Messages
  • rahed
    Oct 14, 2008
    • 0 Attachment
      > I tried changing the SOAP version to 1.1 just to send the content-
      > 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.

      You can change the content-type with

      $soap->transport->http_request->header('Content-type' => 'text/xml');

      --
      Radek
    • Show all 5 messages in this topic