"Sean D. Ackley" wrote:
> So, in fact, when Analog identifies which browser strings go with which browser
>summary options, isn't this something we can add into the configuration? Or, does
>this need to be programmed into the source code?
It is built into the program. Analog recognizes the de facto user agent string like,
Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)
And parses it out into
{Browser}/{Major Version}.{Minor Version}
It then parses the rest of the string for specifics, like OS, MSIE, etc. Analog
understand differing strings for different browsers (like Netacape's "Macintosh; ...;
PPC" vs Microsoft's " Mac_PowerPC").
Some robots will work patially:
FAST-WebCrawler/2.0.9 ([EMAIL PROTECTED];
http://www.fast.no/faq/faqfastwebsearch/faqfastwebcrawler.html)
Can be parsed into the summary (with SUBBROW */*.*) as
Fast-WebCrawler
Fast-WebCrawler/2
Fast-WebCrawler/2.09
But it has no recognizable OS.
The WAP device "WinWAP 2.2 WML 1.1" probably won't get parsed, because it doesn't
comply to the de facto standard.
> For instance, is there, or can there be a definition file that has all the browser
>strings, and then listed next to it the category they fit into for the summary
>report? This could give customization for people who have abnormal browser strings
>on their websites, like the WAP stuff.
You could do something with Aliases to make the items fit:
BROWALIAS "WinWAP *" "WinWAP/*"
HTH,
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
