why don't you just run a separate report for spiders-only? might even be
easier to read.
> -----Original Message-----
> From: Dave Atkins [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2001 9:21 PM
> To: [EMAIL PROTECTED]
> Subject: [analog-help] banning spiders from page counts
>
>
> I've tweaked analog a fair amount already, but I'm not sure
> about how the
> exclude commands work.
>
> Here is what I want to do:
>
> In the general summary, I want to exclude all requests for
> pages which come
> from browser types I know to be spiders. However, I need the
> data on these
> requests to show up in the browser report because our site
> managers need to
> know when their sites are being spidered.
>
> I know I can do a
>
> BROWEXCLUDE Atomz* and/or
> HOSTEXCLUDE 64.41.203.238,216.35.140.230
>
> for example, but then I lose that traffic completely. I had a
> similar issue
> with a "page" we do not count and I was able to exclude it via:
>
> PAGEEXCLUDE /redirect.asp
>
> similarly, I was able to tag an image we use on a remote site
> to be counted
> as a page via:
>
> PAGEINCLUDE /search/nocache.gif
>
> Is there anyway to categorize requests from certain browser
> types as "not
> pages"?
>
> Thanks in advance (again!)
>
> Dave Atkins
> ConsumerReview.com
>
> --------------------------------------------------------------
> ----------
> 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]/
> --------------------------------------------------------------
> ----------
>
------------------------------------------------------------------------
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]/
------------------------------------------------------------------------
