The simpliest way to test if that is the issue is to
connect to some
other resource, say a simple HTML page via HTTPS and see if you
connect cleanly.
--
Dave Wolf
Cynergy Systems, Inc.
Adobe Flex Alliance
Partner
http://www.cynergysystems.com
http://www.cynergysystems.com/blogs
Email: [EMAIL PROTECTED]stems.com
Office: 866-CYNERGY
--- In [EMAIL PROTECTED]ups.com,
"Matt Chotin"
<[EMAIL PROTECTED]> wrote:
>
> It might be a problem with a self-signed certificate. You may need to
> update your computer to accept self-signed without prompting (I don't
> remember how to do that at the moment). If this isn't set no prompt
> will appear but no connection to the HTTPS destination will work either.
>
>
>
> Matt
>
>
>
> ________________________________
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
> Behalf Of vitopn
> Sent: Thursday, September 07, 2006 6:07 PM
> To: [EMAIL PROTECTED]ups.com
> Subject: [flexcoders] Error #2032 HTTPS IE only
>
>
>
> I am unable to get the SecureHTTPChannel to work in IE. In particular
> I'm trying to use the channel to connect to a set of dataservice
> destinations. I've experimented with my own client as well as with the
> flexcab sample.
>
>
>
> This is the error I get:
>
> [RPC Fault faultString="Send failed"
> faultCode="Client.Error.MessageSend" faultDetail="Channel.Ping.Failed
> error [IOErrorEvent type="ioError" bubbles=false
cancelable=false
> eventPhase=2 text="Error #2032: Stream Error. URL:
> https://localhost:8443/samples/messagebroker/httpsecure
> <https://localhost:8443/samples/messagebroker/httpsecure>
"]"]
> at
> mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal:
> :dispatchFaultEvent()
> at ::DataListRequestResponder/fault()
> at mx.rpc::AsyncRequest/fault()
> at mx.messaging::ChannelSet/::faultPendingSends()
> at mx.messaging::ChannelSet/channelFaultHandler()
> at
> flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEven
> tFunction()
> at flash.events::EventDispatcher/dispatchEvent()
> at mx.messaging::Channel/mx.messaging:Channel::connectFailed()
> at
> mx.messaging.channels::PollingChannel/mx.messaging.channels:PollingChann
> el::connectFailed()
> at mx.messaging.channels::HTTPChannel/::pingErrorHandler()
> at ::ChannelRequestLoader/::callEventCallback()
> at ::ChannelRequestLoader/::ioErrorHandler()
> at
> flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEven
> tFunction()
> at flash.events::EventDispatcher/dispatchEvent()
> at flash.net::URLLoader/flash.net:URLLoader::redirectEvent()
>
> In each case all works well in firefox and IE works if I am using
> HTTPChannel instead of the SecureHTTPCHannel.
>
>
>
> I have tried using a self generated certificate and a trial certificate
> from verisign. For each certificate I also added the required
> certificate to the CertificateAuthorities store so that I did not get
> any warnings in the browser.
>
>
>
> Is this a problem with self generated or trial certificates?
>
>
>
> Any information would be appreciated.
>
>
>
> Cheers,
>
> -Vito
>
