Re:Microsoft decides to automatically update Internet Explor...
by pyre on Thursday December 15, 2011 @11:04AM
(#3356660)
Adding a single header can be done as simply as using nginx as a 'transparent' proxy in front of the app. No need to make application changes.
Re:Microsoft decides to automatically update Internet Explor...
by AmazingMe on Thursday December 15, 2011 @10:43PM
(#3359309)
or can be added to policy/registry that open http://legacyapp:6583 in ie6 frame.
There's a reason companies can't upgrade from IE6 without a significant cost, and it is usually one of the following:
1) The company has lost the sourcecode, and the original engineers have left.
2) The company doesn't even have the source code, and has no rights to modify the application.
3) The application is vendor-supplied, and said vendor requires a large cash payment to make the 'custom' change.
4) The application is vendor-supplied and the vendor refuses to support IE6 in the version of their application that the company have deployed. Their new, super expensive version does support more browsers.
5) The company has little control over their IT. Their business depends on a thousand tiny applications built by countless different parties of varying ability. Simply auditing the whole mess is too costly.
So lots of companies take the easy (and cheap) route out and decide to stick with an ancient browser.