Sounds like the request isn¹t even hitting the server. That would be my guess otherwise you would at least see the return header. I have always found it useful to use restclient 2.2 on google code as you get a cool little gui to manually set HTTP header values, authenticate as part of the request. You can also persist requests to disk as well. It¹s a jar so you will have to call it directly from the command line but I think Dustin did provide some documentation. If not, let me know and I¹ll give a hand.
K On 5/16/09 10:02 AM, "Terry May" <[email protected]> wrote: > > > > > > Hi everyone, long time reader, first time poster. > > I am using Blaze DS as an HTTP proxy to talk to a RESTful webservice. I have > a very simple MXML document with an HTTPService that defines an AMFChannel. > > When the HTTPService throws a fault event, I need to access the HTTP headers > and the message.body, but they are always null. > I have looked at the AMF stream coming back from the proxy with charles and it > doesn't look like the info I need is in the response at all! > > Does anyone have any experience with this? am I perhaps missing a server side > configeration? or does Blaze just not send me that info (omg that would hurt > if it is the case) > > Thanks in advance for any help, as I am at the end of my rope with this. > > > Terry May > Detroit Area Adobe User Group Manager > > > >>
