Try hardcoding your url in the endpoint in services-config.xml
I created this services-configAIR.xml file and it works for AIR.
I also use this for SSL Flex apps, but without the hardcoded
"http://www.synapsenow.com/flex2gateway/"; url
Don
<?xml version="1.0" encoding="UTF-8"?>
<services-config>
<services>
<service id="coldfusion-flashremoting-service"
class="flex.messaging.services.RemotingService"
messageTypes="flex.messaging.messages.RemotingMessage">
<adapters>
<adapter-definition id="cf-object"
class="coldfusion.flash.messaging.ColdFusionAdapter" default="true"/>
</adapters>
<destination id="ColdFusion">
<channels>
<channel ref="my-secure-cfamf"/>
<channel ref="my-cfamf"/>
</channels>
<properties>
<source>*</source>
<!-- define the resolution rules and access level
of the cfc being invoked -->
<access>
<!-- Use the ColdFusion mappings to find CFCs,
by default only CFC files under your webroot can be found. -->
<use-mappings>false</use-mappings>
<!-- allow "public and remote" or just
"remote" methods to be invoked -->
<method-access-level>remote</method-access-level>
</access>
<property-case>
<!-- cfc property names -->
<force-cfc-lowercase>false</force-cfc-lowercase>
<!-- Query column names -->
<force-query-lowercase>false</force-query-lowercase>
<!-- struct keys -->
<force-struct-lowercase>false</force-struct-lowercase>
</property-case>
</properties>
</destination>
</service>
</services>
<channels>
<channel-definition id="my-cfamf"
class="mx.messaging.channels.AMFChannel">
<endpoint uri="http://www.synapsenow.com/flex2gateway/";
class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>false</polling-enabled>
<serialization>
<instantiate-types>false</instantiate-types>
</serialization>
</properties>
</channel-definition>
<channel-definition id="my-secure-cfamf"
class="mx.messaging.channels.SecureAMFChannel">
<endpoint
uri="https://{server.name}:{server.port}/flex2gateway/";
class="flex.messaging.endpoints.SecureAMFEndpoint"/>
<properties>
<add-no-cache-headers>false</add-no-cache-headers>
<polling-enabled>false</polling-enabled>
<serialization>
<instantiate-types>false</instantiate-types>
</serialization>
</properties>
</channel-definition>
</channels>
<logging>
<target class="flex.messaging.log.ConsoleTarget" level="Error">
<properties>
<prefix>[Flex] </prefix>
<includeDate>false</includeDate>
<includeTime>false</includeTime>
<includeLevel>false</includeLevel>
<includeCategory>false</includeCategory>
</properties>
<filters>
<pattern>Endpoint.*</pattern>
<pattern>Service.*</pattern>
<pattern>Configuration</pattern>
<pattern>Message.*</pattern>
</filters>
</target>
</logging>
<system>
</system>
</services-config>
--- In [email protected], "Paul Kukiel" <[EMAIL PROTECTED]> wrote:
>
> Anyone?
>
> From: [email protected] [mailto:[EMAIL PROTECTED] On
> Behalf Of Paul Kukiel
> Sent: Wednesday, 6 February 2008 12:51 PM
> To: [email protected]
> Subject: RE: [flexcoders] Remoting over SSL
>
>
>
> Ok I figured it out I removed the endpoint from the RemoteObject tag
and it
> worked.
>
>
>
> However it won't work when I compile as Air. Is anyone using Remote
Objects
> over SSL in air? Any good references?
>
>
>
> Paul
>
>
>
> From: [email protected] [mailto:[EMAIL PROTECTED] On
> Behalf Of Paul Kukiel
> Sent: Wednesday, 6 February 2008 10:20 AM
> To: [email protected]
> Subject: [flexcoders] Remoting over SSL
>
>
>
> Hi,
>
>
>
> I'm having an issue using remote objects over ssl. I have got this
to work
> in FireFox but not in IE. I have searched around and have added
> <add-no-cache-headers>false</add-no-cache-headers> to the
<properties> tag
> of <channel-definition>
>
> but it's still not working.
>
>
>
> This is the error I am receiving:
>
>
>
> [RPC Fault faultString="Send failed"
faultCode="Client.Error.MessageSend"
> faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed.
>
>
>
> Server is IIS, with CF8. Flex 3 beta.
>
>
>
> Any idea's?
>
>
>
> Thanks.
>
