I rather treat this patch as a _bug_. user:password@host format is used (I have 3 or 4 instances in monitoring system, to allow automatic proxy onto the system with 'guest' user name, for example). To block scam, it was sufficient to restrict username length, or to set up a checkbox in explorer setting. The whole idea is wrong - instead of fixing IE (just show REAL host name, for example), MS decided to drop functionality. We (in our company) adviced people _against_ this patch. It broke legitimate addresses, and fix a very rare and exotic problem... which can be fixed by many other ways.
Sorry -
Mostly non-password encoded forms that don't refresh when you hit submit. After Submitting 3 or 4 times they seem to work. Like most ISP's, we take calls when somebody's web site doesn't work, even if we don't even host it.
On Tue, 2004-02-03 at 12:24, Conrad Golightly wrote:
Can you give us some more detail about what they ARE seeing?
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Herman Harless Sent: Tuesday, February 03, 2004 11:27 AM To: nanog Subject: Latest IE patch breaking non username:password@encoded websites?
We're starting to take complaints from folks who have installed the latest IE patch about various broken website functionality. The complaints are not related to folks trying to use the username:password@ functionality that was removed by the patch.
Is anyone taking similar calls / seeing similar issues?
Herman Harless Director, Advanced Data Network Engineering and Operations NTELOS, Inc. herman@ntelos.net
--- [This E-mail scanned for viruses]