You need to use a SecureAMFChannel to interact with a SecureAMFEndpoint.

It’s not clear from your emails why the server is receiving HTTP requests 
rather than HTTPS requests. If you’re using a SecureAMFChannel on the client, 
its requests will be sent via HTTPS.

If you have something in front of your server that’s handling HTTPS (say a 
hardware SSL accelerator) that passes insecure HTTP requests back to the 
server, you need to mix and match a secure channel class for the hop from the 
client to the SSL appliance, with an insecure endpoint for the hop from the SSL 
appliance to the app server. The config for this would be something like:

<channel-definition id="secure-amf" 
class="mx.messaging.channels.SecureAMFChannel">
    <endpoint url="https://{server.name}:{server.port}/secureamf"; 
class="flex.messaging.endpoints.AMFEndpoint"/>
    …

Note the secure channel class, secure endpoint URL and insecure endpoint class. 
But again, you only need to configure things this way when you have a component 
between the client and server handling SSL.

Hope that helps,
Seth

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of 
venkateswarlu naidu
Sent: Thursday, October 09, 2008 8:23 PM
To: [email protected]
Subject: Re: [flexcoders] Remote calls are not happening using blazeDS in 
secured environment

Here is the exact error message that i am seeing in the server console
secure endpoint /messageborker/secureamf must be contacted via secure protocol

Please help me on this.

Thanks & Regards,
Venkat.


----- Original Message ----
From: venkateswarlu naidu <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, 9 October, 2008 9:33:56 PM
Subject: [flexcoders] Remote calls are not happening using blazeDS in secured 
environment
Hi All,

Even after adding my-secure-amf channel to remote-config. xml, our flex 
application coludn,t make remote calls.
I am seeing a failover to HTTP from a HTTPS request in the http url log, dont 
know why it is failing over to
HTTP://<context>/messagebroker/ amf from HTTPS://<context>/messagebroker/ 
secureamf in a secured environment.

Actually this failover is not happening in DEV (in which we have both HTTP and 
HTTPS enabled).

The problem is specific to QA env (weblogic+clustered +secured) , i dont have 
any clues.

Can any body help me on this?

Thanks & Regards,
Venkat.


----- Original Message ----
From: venkateswarlu naidu <contactvenku@ yahoo.co. in>
To: [EMAIL PROTECTED] ups.com
Sent: Wednesday, 8 October, 2008 10:41:13 PM
Subject: [flexcoders] could not establish connection to java data service from 
flex client using blazeDS
Hi All,

We have a flex+blazeDS+ Java based application, after deploying the application 
in QA env, java data service calls are not happening. When i see the URL log in 
HTTP sniffer tool, the request is getting stopped at URL <context-root> 
/messagebroker/ amf and finally seeing 502 (CANNOT_CONNECT) status.

The same application is working fine in DEV environment.

Our QA environment: secured, HTTPS, running behind firewalls and clustered.

Why the flex client can not connect to the java data services?

Any help is greatly appreciated.

Thanks & Regards,
Venkat.

Reply via email to