OSBlues

I’ve not had this confirmed from any of my contacts at AVG via the Google Group I belong to, but this post on the Australian Whirlpool Broadband Forums, suggests 9th July might bring the release we’ve been waiting for.

I’ve also found Lloyd Borrett posting the same info here.

If I hear any further confirmation from AVG, I’ll let you know, until then we’ll see what happens on the 9th.  Interestingly Lloyd doesn’t see to know what day it is, either that or my calendar is wrong –

In working with the web master community, AVG has responded immediately and on Tuesday, July 9th, AVG will issue a product modification to address the spikes that a few individuals have seen with their web traffic.

Tuesday? I make it Wednesday, ah well, we might see something Tuesday or Wednesday then 😛

Nice use of “a few individuals” there Lloyd, I wouldn’t class it as a few myself.

Now confirmed by Pat Bitton at AVG, see comment below.

:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::

The Register are running a further follow up article “AVG disguises fake traffic as IE6“, which states that AVG are now using a “new” user agent for the paid version of AVG’s LinkScanner.

This has been confirmed by Roger Thompson in the AVG Webscanning Google Group, to which I’m a member.  When asked if it was true Roger said –

..Yes, it’s true, but it’s not quite what it seems. It was a planned
service release that was already in the works when we found out about
the issue, and fixed some other critical issues at the same time.

It changes the User Agent string to SV1, but it leaves some of the
other request headers so that they’re different enough that you can
still parse them out of stats if you want to..

I personally don’t really see this as a “new” user agent, as I’m already filtering my logs for this one.  From what I’ve read, this is the original agent used by LinkScanner before they were purchased by AVG, so it’s already mentioned in my initial AVG log spam post.

That aside, it’s still not a great move from AVG at this point.  They are supposed to be working with the community (myself included) to resolve this from a webmasters point of view, switching (well mixing in another) user agent at this point is a little silly.

At this point I need to credit Michael Ducy who tipped me off this change yesterday, he however claims it’s affecting the free version also –

AVG changed the user agent with the latest release. They now use “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)”. I confirmed this by downloading and installing AVG free this morning and using wireshark to sniff the traffic.

The saga continues..

:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::