httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: [Fwd: [Fwd: Browser capabilities?]]
Date Wed, 01 Oct 1997 01:42:37 GMT
The desire is to be able to distinguish between clients which are being
controlled by a human at that moment, and clients which are uncontrolled. 
The former are considered for "ad impressions", the latter are considered
for robot control rules (such as "hey you crawler, I told you not to go
there and now you're recursing infinitely! stop!").  Yup the latter can
also be done somewhat well enough with robots.txt ... but if the
user-agent distinguishes between the two modes then a bug in a distributed
browser implementation does not become a problem.

But mostly it's 'cause of ad impressions (at least for the folks I deal
with).  Rob probably wants it mostly for robot control reasons. 

If you can forward that on to netscape's techies that's great.  I know
folks at one of the content partners that have been trying to get their
rep (who I'm guessing is not tech) to understand the issue. 


On Thu, 25 Sep 1997, Maj Justin Seiferth wrote:

> Do we need to get Netscape's ear?  Hear it is- it someone will forward
> the suggestion to me I'll work to get it into the feature list.
> justin
> >   Presume you're aware of this issue if not let me know.  Hate to see
> > > MSIE getting three cheers for anything.
> >
> > It sounds as if you're asking if Communicator could send out one user
> > agent when doing normal web surfing, and one when doing off-line
> > browsing (i.e., what Netcaster does).  It that what the issue is?
> >
> > If so, I'd be more than glad to send a note to the Netcaster product
> > manager and submit this as a request for enhancement to the next
> > Netcaster release.  However I'm interested: did the discussion clarify
> > exactly why this was a desired capability?  (I can guess, but I thought
> > you'd be able to give me more info.)
> >

View raw message