Use the proxy service that ships in BlazeDS and LCDS for your Http requests.
There are a variety of browser hacks related to Http headers (which in some cases also impact SOAP web services), and the player is likely to get more restrictive in this area rather than less. This generally has more to do with lax or faulty APIs in routers, etc., but we as Flash users end up suffering. To side-step the header restrictions, as well as the limited set of Http methods supported by the Player and browser plugin APIs, if you use HTTPService or WebService with useProxy="true", and route those requests through BlazeDS or LCDS, your desired request is wrapped and sent in a compliant fashion from the Player to the proxy service, and it is then unwrapped and the actual proxied request can be made successfully. This service also handles getting Http error responses (say, in the 500 status code range) back into the Player usefully. Best, Seth ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of gli1_2000 Sent: Thursday, February 07, 2008 9:14 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: HTTPService or URLRequest Request header Question Then what is a possible alternative to get around this? Anyone has suggestions? --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , João Fernandes <[EMAIL PROTECTED]> wrote: > > this is true, you can't use authorization token in headers anymore > within Flash Player. > > This is big step backwards in my opinion > -- > > João Fernandes > > http://www.onflexwithcf.org <http://www.onflexwithcf.org> > http://www.riapt.org <http://www.riapt.org> >
