It is anyone able to answer question and / or find a remedy?: http://www.msfn.org/board/topic/175153-ie8-and-the-web-pages-https/ TH. P.S. Please correct HTPPS with HTTPS.
hmm, please tell my why i should mind on IE8? you read that IE8 is dropped dead since january? latest IE for Vista is IE9, Windows 7 and newer IE11, those are supported, any other old version gets no longer updates so is vulnerable.
And since that PC is using a Windows Embedded POSReady 2009 OS, IE8 will be Supported until June 2019. Besides the answer you have received already in that forum, that particular domain page HTML source does not contain this tag: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> found in other pages of the same site. It means you can not see that page in an older browser. Read Specifying legacy document modes to understand why. The remedy is for the Webmaster of that site to include the compatibility Meta tag, so older browsers can see that page.
Actually, that's probably the registry hack for Windows XP. I'd upgrade to a more modern 3rd part browser, since keeping up-to-date is the whole point of the hack right?
I left XP behind years ago, so I don't know, however, are you sure it is a hack? https://www.microsoft.com/en-us/download/details.aspx?id=11196
https://www.wilderssecurity.com/thre...etup-these-days.111264/page-1501#post-2562522 http://www.zdnet.com/article/registry-hack-enables-continued-updates-for-windows-xp/
that hack makes windows illegal (it violates license agreement) and it is not proven that all updates from posready are full compatible - because none is writing about hack and having trouble - none to blame . if someone is using that hack he should get along with its afterward trouble himself. my viewpoint.
They are all compatible. At least up to now. Less likely for .NET Framework. That must be done manually. It is not notified by Microsoft Update. Better to uninstall all NET.
Whether or not you can hack an outdated OS and claim support for an outdated browser, know that most webmasters do not care and will not support your choice. We do not go out of our way to program anything for such situations, and I don't expect others to either. My recommendation is as others have made. Use an up to date 3rd party browser.
IE8 on XP only supports TLS 1.0, which is not the most secure, though almost all sites with TLS 1.2 still support TLS 1.0 as well, they do not support a lot of old ciphers. You can see here (https://www.ssllabs.com/ssltest/viewClient.html?name=IE&version=8&platform=XP) that IE8 mainly supports weak and insecure ciphers and the ones that aren't labeled as such are still not considered as secure as most modern ciphers, and those particular ones are also not widely supported as they're slower. Your example site on MSFN doesn't support any of the old IE8 ciphers: https://www.ssllabs.com/ssltest/analyze.html?d=malwaredomainlist.com My recommendation is also as others have made to use an up to date 3rd party browser. Even though you may still get security fixes for specific vulnerabilities, IE8 is not regarded as secure as other browsers in general and the security of HTTPS connections made by IE8 is also limited by it's lack of support for newer standards.