Forum Moderators: mack

Message Too Old, No Replies

Microsoft URL Control 6.00.8862

hmm what is that for a bot

         

zeus

9:59 am on Aug 25, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I have never seen that before, but I was heavy on mysite yesterday and today.

zeus

11:30 am on Aug 27, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



nobody know, well maybe its time to block it.

Mokita

12:59 pm on Aug 27, 2006 (gmt 0)

10+ Year Member



[webmasterworld.com...]
[webmasterworld.com...]

It looks like something you will probably wish to block.

msndude

1:24 am on Aug 29, 2006 (gmt 0)

10+ Year Member



Around the mid 1990s, we (Microsoft) shipped an ActiveX control called the Internet Transfer Control, which allowed developers to write programs to transfer files with FTP or HTTP.

[msdn.microsoft.com...]

Although this isn't documented in MSDN, the control always set the user-agent to "Microsoft URL Control" plus a version number. It was possible to change that, but it was quite a pain, so few did.

This actually caused some problems when people upgraded to the .NET Framework because the replacement API actually required a user-agent string, and some customers coudln't figure out what to put there. (Apparently some opted for the space character. Has anyone seen that in the real world?)

Of course there are plenty of old machines (and old software) still around. It is perfectly possible that a legitimate program is somehow doing this, but most of the traffic I see on the web suggests that the typical program that does this is an e-mail-address-stealing crawler. I'd guess that someone wrote one of these once upon a time and that lots of other people have simply copied and tweaked it since then.

You cannot block this with robots.txt; the code is older than the robots.txt specification, so the programmer would actually have to write extra code to read, parse, and respect robots.txt. That seems very, very unlikely. :-)

On the other hand, if you do go to extra trouble to block the user-agent, it won't be completely trivial for them to update their programs to work around it. A real programmer can do it, of course, but a script kiddie might be stymied. Like I said, we didn't make it easy to do, and there is no support for this now.

Hope that helps. Sorry to hear that someone is doing this to you.