You should add back the normal AMFChannel definition
(that transports messages over HTTP) as it will coexist with the
SecureAMFChannel definition (that transports messages over HTTPS). As stated
before, because both channels use the same servlet mapping in their endpoint
addresses the mess
I replied to the Adobe forums - the requirement to add some
path info to your secure AMF channel endpoint was, in spirit, correct... here's
what I posted:
"I just want
to restate knallore's poste regarding channel definitions as it is essentially
correct, but the issue was that he didn't
On Wednesday 27 September 2006 16:58, syndrake7 wrote:
> (mx.rpc:Fault)
> faultCode = "Client.Error.MessageSend"
> faultDetail = "Channel.Connect.Failed error
> NetConnection.Call.Failed: HTTP: Failed"
> faultString = "Send failed"
> details = "https://me.com/flex2gateway/";
> level = "error"
Can
On Wednesday 27 September 2006 15:00, syndrake7 wrote:
> I don't think the problem is caused by the services-config file I
> used to compile my Flex app. I think the problem is with ColdFusion
> and how it has defined endpoints for /flex2gateway/, which works
> fine with http: but not with https:.
On Tuesday 26 September 2006 18:27, syndrake7 wrote:
> Background: I can browse to http://me.com/flex2gateway/ and receive
> a blank page with no errors. I cannot browse to
> https://me.com/flex2gateway/ - I get an HTTP: Status 500 error. The
> SSL cert is setup correctly on the server (I can brows
5 matches
Mail list logo
