Forum Moderators: open

Message Too Old, No Replies

AOL UA's

         

wilderness

1:04 pm on Feb 16, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Might anybody keep track of them?

Do they ALL contain "AOLBuild" in the UA?
Before my hiatus the majority did not?

From this morning:

"Mozilla/4.0 (compatible; MSIE 8.0; AOL 9.0; AOLBuild 4327.271; Windows NT 5.1; Trident/4.0; SearchToolbar 1.2; GTB7.2; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; AskTbPSI/5.13.1.18107)"

Is AOL 9.5 the latest version?

My sites have always had a high percentage of AOL visitors, which I had forgotten.

TIA

lucy24

8:46 pm on Feb 16, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



There's definitely an AOL 9.6. Both of these seem to be humans in spite of the dubious UA:

Mozilla/4.0 (compatible; MSIE 8.0; AOL 9.6; AOLBuild 4340.5004; Windows NT 6.1; WOW64; Trident/4.0; GTB7.2; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; HPDTDF; .NET4.0C)

Mozilla/5.0 (compatible; MSIE 9.0; AOL 9.6; AOLBuild 4340.168; Windows NT 6.1; WOW64; Trident/5.0)

There's also an AOL 10.1 but I'm not clear whether this is an AOL robot or a human using AOL search:

64.12.117.71 - - [12/Jan/2012:10:41:20 -0800] "HEAD /directory/filename.html HTTP/1.1" 200 270 "-" "Mozilla/4.0 (compatible; MSIE 7.0; AOL 10.1; AOLBuild 2.1.103.1; brand=aol; Windows NT 6.0; Trident/5.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET4.0C; .NET CLR 3.0.30729)"

I double-checked the IP. Similar from 205.188.116.204, also an AOL IP. Notice how it's got a later AOL number but earlier MSIE number? Also a completely different number configuration for the "AOLBuild" part.

The distinguishing feature of AOL is that the IP changes every time. Ten images = ten IPs. Not huge changes like a botnet, just little twitches in the ddd area. But this kind of thing is probably more useful for people running their own servers. I just know it plays havoc with log wrangling. (The code looks for html + favicon from the same IP at around the same time.)

wilderness

2:38 am on Mar 13, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Anybody have a clue if this a user or the cache?
All image requests were HEAD checks and and a single root URL.

Mozilla/4.0 (compatible; MSIE 6.0; AOL 9.0; Windows NT 5.1; SV1; GTB6; .NET CLR 1.1.4322)

twenty-five minutes later the same requests were repeated.

When did AOL stop using the simple "Mozilla Ver" for their cache and head checks?

MSIE 6.0 slightly old.
I've no clue what Ver the GTB is up to.