This content has been marked as final. Show 3 replies
Quoting Carson Hager, of Cynergy, "This is currently a limitation in the Flash Player ( all versions ). SOAP faults require HTTP 500 to returned. When the FP sees a 500, it stops reading data from the socket. The current workaround is to use the proxy or to use some other mechanism to change the HTTP status code to 200 before the FP receives it. Yes I realize that this is pretty poor and has serious limitations."
Google this you find much discussion.
Rats, that's too bad.
I'll see if I can figure out a way to change the response code ASP.NET sends when it throws an exception. I'm guessing that you can't... but it won't hurt to do some searching.
I have seen some solutions, but don't recall any .net ones.
If you have control, consider using HTTPService with ASP.NET instead of WebService. It is easier to use, somewhat faster, and maybe easier to control exception handling. That is my choice of back-end / integration technologies.