IE will tell us the status code (404 or 500) but it won't give us the body of the HTTP packets which would include the details. Mozilla doesn't give us either. Until the browser can provide us with this info it won't be addressed, though we are trying to push for it in the timeframe of the next major Player release.
Matt ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of paulwelling Sent: Tuesday, March 20, 2007 1:09 PM To: [email protected] Subject: [flexcoders] Re: WebService Fault Handling - Flash Player 9 Update Hello, Thank you for the response. A malformed WSDL string set in the WebService will cause a 404 with the following error, that does get passed to the FlashPlayer: Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL. Is it only Faults - 500, that won't get passed to the FlashPlayer when run without a proxy? Is it realistic to expect that this issue will get addressed in the short-term? Thank you, Paul --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Matt Chotin" <[EMAIL PROTECTED]> wrote: > > Unfortunately we cannot fix this without support from the browser > vendors. We are in discussions with them to try to have the right > information accessible to plugins in some of their next versions. > > Matt > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of paulwelling > Sent: Tuesday, March 20, 2007 8:59 AM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] WebService Fault Handling - Flash Player 9 Update > > > > Hello, > > I just examined the latest FP9 Update Fixed Issues web page, and see > no mention of the WebService Fault Handling Issue (fault body not > passed to player) that has been discussed many times here... > > This is a really big issue for people not using a proxy, and I'm > surprised that more of us haven't asked Adobe for this to be a > priority fix, or at least come up with a real work around. > > Can someone tell me when this will be addressed..? > > Thanks, > Paul >
