Your blazeds http transport is going fine, otherwise you wouldn't see anything in message, faultcode, etc. The problem is either in the proxy server itself, or the server you're trying to talk to.
-Josh On Tue, Jul 29, 2008 at 3:33 PM, ron_mori <[EMAIL PROTECTED]> wrote: > I must be missing something obvious - > > Using an httpService proxy to the backend server like so in my > proxy-config: > <destination id="backEnd"> > <properties> > <url>http://myServer:8080/myApp</url> > </properties> > </destination> > > Executing a simple test, I monitor the traffic on the client > (Wireshark) and find the desired xml body in the response http 1.1 > status 500 Internal Server Error message from the backend server. > > Dumping the FaultEvent in the client (ObjectUtil.toString()) contains: > ... > fault = (mx.rpc::Fault)#18 > errorID = 0 > faultCode = "Server.Proxy.Request.Failed" > faultDetail = "HTTP/1.1 500 Internal Server Error" > faultString = "HTTP/1.1 500 Internal Server Error" > message = "faultCode:Server.Proxy.Request.Failed > faultString:'HTTP/1.1 500 Internal Server Error' faultDetail:'HTTP/1.1 > 500 Internal Server Error'" > name = "Error" > rootCause = (null) > ... > Also the '.result' is null. > > So no sign of the response xml body. Again this was a faultEvent. > ------ > I thought, might the proxy-config default channel of my-amf be > incorrect? Since I'm working with http, I tried the my-http channel > but that threw an exception. > > in a word: help. > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
