ppened and the " FaultEvent.message.headers.DSStatusCode" can sometimes
return the exact server code.
-Mark
-Original Message-
From: Dan Nailor [mailto:dnai...@emarketinginc.com]
Sent: Tuesday, February 05, 2013 12:23 PM
To: dev@flex.apache.org
Subject: HTTPService Response
s that I had to change the rpc package of the
flex sdk.
hope that this is useful to someone!
[1] https://gist.github.com/davidcoleman007/4717928
Cheers!
-Dave
> From: dnai...@emarketinginc.com
> To: dev@flex.apache.org
> Date: Tue, 5 Feb 2013 14:16:54 -0700
> Subject: RE: H
From: Rick Winscot [mailto:rick.wins...@gmail.com]
Sent: Tuesday, February 05, 2013 10:58 AM
To: dev@flex.apache.org
Subject: Re: HTTPService Response Headers
Dan.
If you are not using a proxy service like BlazeDS... anything other than an
HTTP200 is going to cause your Flex application fits.
server you send a 500, triggering the flex IOError, then you include in the
> text some JSON or other info that describes the error condition. This
> allows you to know that a 200 is ONLY good data (short of a total server
> meltdown).
>
> From: david_coleman_...@hotmail.com
> To: de
then you include in the text some JSON or
other info that describes the error condition. This allows you to know that a
200 is ONLY good data (short of a total server meltdown).
From: david_coleman_...@hotmail.com
To: dev@flex.apache.org
Subject: RE: HTTPService Response Headers
Date: Tue, 5 Feb
rs,
>
> Rick Winscot
>
>
>
> On Tuesday, February 5, 2013 at 12:22 PM, Dan Nailor wrote:
>
> > Hello,
> > I am looking to find out if there is anything in the works to allow the
> > HTTPService response headers to be interrogated beyond successful and
in the works to allow the
> HTTPService response headers to be interrogated beyond successful and
> unsuccessful calls? From what I understand this is not possible with the
> current class and may be a limitation of some browsers.
>
> http://help.adobe.com/en_US/FlashPlatform/reference/ac
Hello,
I am looking to find out if there is anything in the works to allow the
HTTPService response headers to be interrogated beyond successful and
unsuccessful calls? From what I understand this is not possible with the
current class and may be a limitation of some browsers.
http