Bug #4536
closedIE6 causes socket connection error on download
0%
Description
When attempting to download with IE6 - there is a "Broken pipe" SocketConnection exception thrown when flushing the response.
Updated by ben leinfelder about 15 years ago
googling around for solutions has not shed any light on this error...and it does work with IE7 and IE8...
Updated by Mark Urban-Lurain about 15 years ago
(In reply to comment #1)
googling around for solutions has not shed any light on this error...and it
does work with IE7 and IE8...
Is it possible to test for the browser and then, if the user is using a browser we have not verified works, warn the user and give a list of validated browsers?
Updated by Matt Jones about 15 years ago
Putting up a warning on browser detection sounds like a decent idea to me -- probably test for FF>= 3, IE >= 7, and Safari >= 4, and give a warning for everything else.
The browser market changes fast, and at this point supporting IE6 and other older browsers that are not standards-compliant seems like too much work at this prototype stage. The share of the market for IE6 is rapidly declining (7-10% at this point), and so by the time we go production it would likely be totally out of contention. Here are two browser version sites to give an idea of relative importance of different versions of each browser:
http://gs.statcounter.com/#browser_version-na-monthly-200810-200911
http://www.w3schools.com/browsers/browsers_stats.asp
Updated by ben leinfelder about 15 years ago
added alert message about supported browsers if IE is detected.