Hi Joe, thanks for locate the problem. I think this would be hard for use without having experience/access to a WebOrb and touch here and there trying.
I just tried to remove the charset as you suggested and tried with the example and all works ok, so I removed it. Here's the commit: https://github.com/apache/royale-asjs/commit/a6ab9e91c64fb482c9585c9bc046b14bb5900ab8 I understand that you're now working fine with RO in WebORB. Let us know if you find some other issue. Thanks for reporting this! :) Carlos El mié., 15 ago. 2018 a las 2:50, JoeBoxer (<[email protected]>) escribió: > Hello Carlos and Alex. > > It seems WebORB doesn't like the Content-Type being set as > "application/x-amf; charset=UTF-8". It matches up the content-type with > internal parsers depending on how you are using it so it's expecting > Content-Type "application/x-amf". > > In the AMFNetConnection.as file > > xhr.setRequestHeader("Content-Type", "application/x-amf; charset=UTF-8"); > > would need to be > > xhr.setRequestHeader("Content-Type", "application/x-amf"); > > Thanks again for taking the time to look into this. Not sure how to > address > this unless I compile my own version everytime. Any suggestions? > > Regards > > > > -- > Sent from: http://apache-royale-users.20374.n8.nabble.com/ > > -- > Carlos Rovira > http://about.me/carlosrovira > > <http://apache-royale-users.20374.n8.nabble.com/> > >
