Josh, I think you are right, the OP was not adding headers to the HTTP request after all, and his header was not "Authorization", which as you point out, is again allowed.
Probably best to ignore me on this one! Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Thursday, June 12, 2008 6:30 PM To: [email protected] Subject: Re: [flexcoders] Re: My Web Service with soap headers code no longer work with Flex 3 I was under the impression Auth headers were allowed again? http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403030&sliceId=1 <http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403030&sliceId=1> But, being a SOAP header I think it's part of the POST request and the flash HTTP header blocking stuff wouldn't apply anyway? -Josh On Fri, Jun 13, 2008 at 2:56 AM, Tracy Spratt <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: I see that your header is an authorization header. That is not good news for you, and your problem cannot be fixed by the crossdomain file. You can no longer set Authorization headers. Below is copied from an earlier post to flexcoders. I think you will find more info if yo search. Tracy 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: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On Behalf Of gli1_2000 Sent: Thursday, February 07, 2008 9:14 AM To: [email protected] <mailto:flexcoders%40yahoogroups.com> Subject: [flexcoders] Re: HTTPService or URLRequest Request header Question Then what is a possible alternative to get around this? Anyone has suggestions? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> <mailto:flexcoders%40yahoogroups.com <mailto:flexcoders%2540yahoogroups.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 ________________________________ From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Tracy Spratt Sent: Thursday, June 12, 2008 12:15 PM To: [email protected] <mailto:[email protected]> Subject: RE: [flexcoders] Re: My Web Service with soap headers code no longer work with Flex 3 There were some security changes in the Flash Player that can affect webservice access. Search for my post: FYI: WebService, FP version 9.0.124.0, "Security error accessing URL" crossdomain.xml fix Tracy ________________________________ From: [email protected] <mailto:[email protected]> [mailto:[email protected] <mailto:[email protected]> ] On Behalf Of Josh McDonald Sent: Thursday, June 12, 2008 9:14 AM To: [email protected] <mailto:[email protected]> Subject: Re: [flexcoders] Re: My Web Service with soap headers code no longer work with Flex 3 I don't know much about funky soap headers, but what kind of error are you getting? Or is it just dropping the headers? On Thu, Jun 12, 2008 at 11:02 PM, Mark <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Any ideas on this? I'm having a real hard time here. Mark --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Mark" <[EMAIL PROTECTED]> wrote: > > In Flex 2 this works like a charm but not in 3, I can't seem to find > any info on the changes in the Help. Can someone lend a hand? > > <?xml version="1.0" encoding="utf-8"?> > <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml > <http://www.adobe.com/2006/mxml> " > layout="absolute" creationComplete="onCreationComplete()"> > <mx:Script> > <![CDATA[ > // > import mx.rpc.soap.SOAPHeader; > import mx.rpc.events.FaultEvent; > import mx.rpc.events.ResultEvent; > import mx.utils.ObjectUtil; > // > /** > *** BEGING WEB SERVICE CALL WITH ADDING HEADERS *** > */ > private function onCreationComplete():void { > trace("GETTING"); > var qName:QName = new QName > ("http://radar.net/RadarXML.asmx <http://radar.net/RadarXML.asmx> > ","AuthHeader"); > var headerInfo:XML = <AuthHeader xmlns="http://tempuri.org/ > <http://tempuri.org/> "> > > <UserName>admin</UserName> > > <Password>admin</Password> > </AuthHeader>; > var header:SOAPHeader = new SOAPHeader (qName, headerInfo); > ws.addHeader(header); > sendData(); > } > // > private function sendData(): void { > trace("SENDING"); > ws.PullXML.send(); > } > // > private function onFault(event:FaultEvent): void { > trace( "FAULT\n" + ObjectUtil.toString( event.fault )); > } > // > private function onResult(event:ResultEvent): void { > trace("RESULT\n" + event.result); > } > // > ]]> > </mx:Script> > <!-- web service --> > <mx:WebService id="ws" wsdl="http://radar.net/RadarXML.asmx?WSDL > <http://radar.net/RadarXML.asmx?WSDL> " > showBusyCursor="true"> > <mx:operation name="PullXML" result="onResult(event)" > fault="onFault(event)"/> > </mx:WebService> > </mx:Application> > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
