This fix would be to improve testing for the iftw win32 bundles.

Currently our iftw.exe's will first check java.sun.com to see if it can connect. If not, it pops up and error saying that users do not have a valid proxy connection. This has been in the code since the 1.4.2_01 wrapper was introduced.

If we build a iftw that is hosted at http://sqesvr.sfbay, the iftw will first check java.sun.com. If the user is on the SWAN, and they are directly connected to the internet (without a proxy), they should be able to run the iftw from http://sqesvr.sfbay. But our current iftw won't allow it.

This should not affect officially deployed iftw's on java.sun.com.

I think we should have our iftw dynamically check the url that the msi file is located at to see if it has a valid connection.
###@###.### 2004-03-16