Channel login error with HTTPS connection

Question

Hi!
I have developed a Flex application which relies on remote object invocations to BlazeDS. I have applied custom authentication to the AMF channel, so login is required to invoke remote objects over the channel.
Application worked perfectly in development environment but at production environment I cannot get channel sucessfully logged in. I have debugged application and no response is obtained from server after channel.login() invocation. Backend resides on Apache Tomcat that listens on port 80. Server is fronted by a Proxy Server that sets HTTPS protocol (https://domain:80/context is set at browser URL although I request http://domain:80/context).
At development environment requests where made with HTTP protocol so I wonder if this issue is related with the HTTPS protocol present in the new server.
Do I need to configure my channels to use secure (HTTPS) communications? Why am I not getting any error response from channel login operation?
I reviewed server logs and It seems login AMF invocation are been tracked but I cannot get any response.
Thank you in advance.

Answer 1

Thank you Alex.
I've set this configuration in services-config.xml. First I tried using SecureAMFEndpoint but then I got an exception on Server that said a secure destination was needed (as it was secured) but was not receiving a secured request. I saw a post in a forum that said AMFEndpoint must be used instead of SecureAMFEndpoint when SSL is applied to a proxy that redirects request to Tomcat, not to Tomcat itself, and this is my case.
<services-config>
    <services>
        <service-include file-path="proxy-config.xml" />
        <default-channels>
           <channel ref="amf-channel"/>
        </default-channels>
    </services>
    <channels>
        <channel-definition id="amf-channel" class="mx.messaging.channels.SecureAMFChannel">
            <endpoint
                uri="https://{server.name}:{server.port}/{context.root}/messagebroker/amf"
                class="flex.messaging.endpoints.AMFEndpoint" />
            <properties>
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
        </channel-definition>
</services-config>
After setting this, channel is succesfully logged in and a remote invocation that is executed inmediatly after channel loggin is completed works OK. But when later I call another remote objects, I get request timeout errors and server is not reached.
Any idea of the issue?