Forum Moderators: open
Guess I'm luck that half-a-dozen MSN updates were added to the end as well ;)
That's not the reason I block it, mind. It's not the only thing that corrupts UAs, although it's certainly a doozy at it. I block it because of one of its "selling" points: high speed download that equates to site ripping.
<Set header Location: tongue-in-cheek.html>
I'm not sure, but that may be a Windows machine with MS software on it.
But that UA string is much too short, and doesn't have enough errors in it.
There's a major patch coming from MS tomorrow. Hopefully, it'll include something that requires an increment in the the .NET Runtime release, so we can get .NET CLR 3.6.something added in there too!
Even better would be if the update forces multiple .NET revisions, like 3.6 and 3.7 -- We might get a really nice and beefed-up UA string then!
<Unset header Location:>
.NET identifier UA tokens are getting ridiculous... What are they thinking? Time for a roll-up guys.
Jim
Note the UA ending of MS"?
It was chopped off by something with a limitation.
Whether it's my own server logs or the users provider is not known. In any event that portion missing by the otherwise standard MSN footprint is as much as sixteen characters, which absent the chop off, would have made the UA even longer.
One example:
MSNbQ002; MSNmen-us; MSNcIA)"
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GoogleT5; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; MS Internet Explorer; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0)
notice the pattern where .NET version goes from High to lower to Higher
It's possible that OfficeLiveConnector and OfficeLivePatch have been around in UAs for some time but I've only just noticed them, mainly because they came in with generally suspect headers.
