What is actually happening under the hood is that IE propagates those security settings down to the OS level. If you use any of the native DLLs to make HTTP/HTTPS calls, they will use settings set in IE (the same goes for Windows Update, any .NET app, etc). This has been the case since Windows 98 and 2000 SP1.
Obviously newer versions of IE (installed by default in W7 and via service packs in Vista) have the TLS settings turned on by default. That is why you are seeing a majority have success with this. I'm surprised that the SSL setting in IE hasn't bit you earlier with another app... but apparently you aren't alone ;P -Nick On Wed, Feb 4, 2015 at 3:55 AM, Paul Hastings <paul.hasti...@gmail.com> wrote: > On 2/4/2015 6:36 AM, Justin Mclean wrote: > >> Hi, >> >> I just tried it on windows, everything went fine without errors. >>> >> > IE8 (64 bit) on windows 7 failed to connect to the > apache-flex-sdk-installer-config.xml URL, getting > > "There is a problem with this website's security certificate.." error. i > went into tools==>advanced==>security & turned on TLS 1.1 & TLS 1.2. IE8 > could connect ok after that. > > next tried the installer again & holy crap worked ok first time. > > this is disturbing at a couple of levels. > > - i suppose IE is as good a choice as any to pick up internet options for > consumer apps but for devs its kind of out in left field. is this > documented anyplace? if not, somebody should probably spread the word. > > - the folks who accounted for the 93% windows successful installs need to > turn in their nerd cards for having a working IE browser ;-) > > > > > > > >
