When we start Flex from an SSL url (and send messages to a
web server with SSL on), one of our SOAP messages gets corrupted.
It only happens with one particular call, and there is another call
which produces almost-identical XML that doesn't encounter the
Using ethereal, we see that the SOAP message looks as follows
(I've removed some parts inside the XML that are well-formed, I've
also modified the IP address). Note that the last n characters from
the XML string have been pasted over the start of the SOAP XML!
If we turn SSL off in the web server (and access the Flex app
using http), it works with no problem.
Have you seen anything like this or know what might be
causing this corruption?
There appears to be a bug where the XML is corrupted if the
file size is too big and SSL is turned on. This happened for XML
somewhere in the range of 8K-9K. To fix the problem, I tried
removing single tags (tried several different ones), and that was
enough to get it to work where there was no corruption. In the end,
I re-named my tags with shorter names and was able to make this
Definitely a work-around and we need to find a "real" way to