2 Replies Latest reply on Mar 30, 2009 11:54 AM by phillipus_rex

    SOAP Response cannot be decoded?

    phillipus_rex
      Does anyone know what can be causing this error:

      The Flash player error is this:

      [RPC Fault faultString="SOAP Response cannot be decoded. Raw response: ‹" faultCode="DecodingError" faultDetail="null"]

      My web debugging proxy is showing this as the XML response:

      Failed to Parse XML Document Reason: Content is not allowed in prolog. Line: 1 Column: 1
        • 1. Re: SOAP Response cannot be decoded?
          Level 7

          "phillipus_rex" <webforumsuser@macromedia.com> wrote in message
          news:gqjba9$c8i$1@forums.macromedia.com...
          > Does anyone know what can be causing this error:
          >
          > The Flash player error is this:
          >
          > [RPC Fault faultString="SOAP Response cannot be decoded. Raw response:
          > ?"
          > faultCode="DecodingError" faultDetail="null"]

          >
          > My web debugging proxy is showing this as the XML response:
          >
          > Failed to Parse XML Document Reason: Content is not allowed in prolog.
          > Line: 1 Column: 1


          Do you have something before this line:
          <?xml version="1.0" encoding="iso-8859-1"?>

          In your response?

          Or maybe something that's not contained within a node, or something that has
          characters in it that are meaningful in XML (such as <) that are not inside
          CDATA tags?


          • 2. Re: SOAP Response cannot be decoded?
            phillipus_rex Level 1
            No, there was nothing before the prolog. Turns out it was a problem with the developer's server side app. It was attempting to decompress a request that was never compressed to begin with.

            We've cleared that hurdle, however, now the app seems to be compressing the data twice and sending gziped data directly to the Flash player - at least that's what Charles and Fiddler are showing.