this is a real PITA. According to Adobe folks over on the flexcoders list, you can setup both a cfamf and cfamf-ssl channel by adding a channel definition and the Flex app will 'auto switch' as needed. I never got this to work though my self. Note also that when you compile your swf against this services-config, it bakes info of this file into your swf. Move your swf to a different server with different services-config setup and bomb out.
Now, what I did with this before was to have my staging and production servers services-config define the cfamf channel with ssl on the server. On my local dev, its defined with no ssl and I have two copies of services-config one called services-config-ssl or something. When ready to deploy, just tell your Ant script ( you are using Ant right? :) ) to point to the ssl one for compiles. If not using Ant, you can change it in FB settings. HTH somewhat DK On Jan 15, 2008 2:57 PM, Sam Singer <[EMAIL PROTECTED]> wrote: > Andy, > Be sure that the root folder on server matches that on your local. > Otherwise, the path to your cfcs will be incorrect. > --Sam Singer > On Jan 15, 2008, at 1:29 PM, Andrew Fox wrote: > > > I've just migrated my first Flex app to our production environment > > and got a "302" error. After searching the web most of the day, the > > solution I've found doesn't work. > > > > I've modified the services-config.xml file to the following as > > recommended: > > > > ================================== > > <channels> > > <channel-definition id="my-cfamf" > > class="mx.messaging.channels.SecureAMFChannel"> > > <endpoint uri="https://{server.name}:443{context.root}/ > > flex2gateway/" class="flex.messaging.endpoints.SecureAMFE > > ndpoint"/> > > <properties> > > <polling-enabled>false</polling-enabled> > > <serialization> > > <instantiate-types>false</instantiate-types> > > </serialization> > > <add-no-cache-headers>false</add-no-cache-headers> > > </properties> > > </channel-definition> > > </channels> > > ================================= > > > > I initially tried it with the {server.port} instead of the hard- > > coded 443 with the same result. When looking at the headers using > > FireFox and the Live HTTP Headers plugin, it calls the https > > version, but now it gives a "500" error on our dev machine that > > accepts both http and https. > > > > Is there some other piece that I'm missing? Do I need to change > > something in Apache or the firewall to allow the flex2gateway to use > > https? I know I can't be the only one who's had this problem. > > > > -- > > Andy Fox > > Systems Analyst III > > Georgia Tech OIT-EIS > > 404-894-4413 > > > > > > > > ------------------------------------------------------------- > > To unsubscribe from this list, simply email the list with > > unsubscribe in the subject line > > > > For more info, see http://www.affug.com > > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > > List hosted by http://www.fusionlink.com > > ------------------------------------------------------------- > > > > > > > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in > the subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it? ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
