Yes, certificates are still useful for Intranet SSL. There’s an important difference between SSH and SSL-without-a-certificate: when you first connect to a server with SSH, your SSH stores the server’s fingerprint. If you then try to connect to what the SSH client believes to be the same machine but gets back a different fingerprint, it … Read more
It is possible to override the compatibility mode in intranet. For IIS, just add the below code to the web.config. Worked for me with IE9. <system.webServer> <httpProtocol> <customHeaders> <clear /> <add name=”X-UA-Compatible” value=”IE=edge” /> </customHeaders> </httpProtocol> </system.webServer> Equivalent for Apache: Header set X-UA-Compatible: IE=Edge And for nginx: add_header “X-UA-Compatible” “IE=Edge”; And for express.js: res.set(‘X-UA-Compatible’, ‘IE=Edge’)