Well, the lesson learned here is -- trust that the services-config.xml file that came with your CF installation is probably properly formatted. Don't make changes unless you know precisely what you're doing. :-)
In all seriousness, though, don't go copying everything from your old installation to your new one. You will overwrite files that are important. You have to manually go through each file and ensure that EXACTLY the same stuff belongs in there on the new CF as did belong there on the old CF. It's painstakingly slow, unfortunately... --- In [email protected], "Warren" <warrenony...@...> wrote: > > Yes, I'm using CF8. I didn't know the endpoints changed in. When you get > all this to work, could you post it. Soon I will be transitioning to CF9 and > would like the benefit of your lessons learned. > > > ----- Original Message ----- > From: Laurence > To: [email protected] > Sent: Friday, February 19, 2010 11:27 PM > Subject: [flexcoders] Re: Still getting Security Sandbox violations... > > > > Ok -- I figured out #2 below... > "flex.messaging.endpoints.SecureAMFEndpoint" in the services-config.xml file > only belongs there in ColdFusion 8. For ColdFusion 9 it's different: > "coldfusion.flash.messaging.SecureCFAMFEndPoint" (Warren's message earlier > said my endpoints were funky -- I'm guessing he's using CF8.) > > So I changed it, and now I'm not getting the 404 error. > > But I still want to know about the secure="false" tag. Will setting that > prevent my channel from being secure? Yet setting it seems to be the only way > I can access my data, which is very stupid if that's going to un-secure my > channel. I mean, what's the point? > > Thanks, > L. > > --- In [email protected], "Laurence" <LMacNeill@> wrote: > > 2) If I go ahead and set secure="false" and leave the domain="*", instead > of getting the Security Sandbox violation, I'm getting a > "Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Status 404: > url: 'https://mydomain.com/flex2gateway/secureamf'" So HTTP 404, that's > file-not-found... What file is it not finding? >
