Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id SAA13061; Tue, 30 Sep 1997 18:42:41 -0700 (PDT) Received: from twinlark.arctic.org (twinlark.arctic.org [204.62.130.91]) by hyperreal.org (8.8.5/8.8.5) with SMTP id SAA13057 for ; Tue, 30 Sep 1997 18:42:38 -0700 (PDT) Received: (qmail 30216 invoked by uid 500); 1 Oct 1997 01:42:37 -0000 Date: Tue, 30 Sep 1997 18:42:37 -0700 (PDT) From: Dean Gaudet To: Maj Justin Seiferth cc: new-httpd@apache.org Subject: Re: [Fwd: [Fwd: Browser capabilities?]] In-Reply-To: <342B13B7.9D1488FD@www.disa.mil> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY=------------9D2A253E386C44F78294D163 Content-ID: Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --------------9D2A253E386C44F78294D163 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: 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. Dean 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.) > > > > --------------9D2A253E386C44F78294D163 Content-Type: MESSAGE/RFC822 Content-ID: Content-Description: Return-Path: Received: from www ([209.22.99.13]) by sleuth.disa.mil (Netscape Messaging Server 3.0) with SMTP id AAA13313 for ; Tue, 30 Sep 1997 14:04:27 -0400 Received: from netscape.com by www (SMI-8.6/SMI-SVR4) id OAA03686; Tue, 30 Sep 1997 14:04:25 -0400 Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id LAA26590 for ; Tue, 30 Sep 1997 11:10:55 -0700 (PDT) Received: from netscape.com ([205.217.232.77]) by judge.mcom.com (Netscape Messaging Server 3.0) with ESMTP id AAA22398 for ; Tue, 30 Sep 1997 11:10:55 -0700 Message-ID: <343140AD.DB07CF60@netscape.com> Date: Tue, 30 Sep 1997 14:10:53 -0400 From: hecker@netscape.com (Frank Hecker) Organization: Netscape Communications Corp. X-Mailer: Mozilla 4.03 [en] (Win95; U) MIME-Version: 1.0 To: seifertj@www.disa.mil Subject: Re: [Fwd: Browser capabilities?] References: <342B08C0.89F51FE8@www.disa.mil> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Maj Justin Seiferth wrote: > 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.) Frank -- Frank Hecker Pre-sales support, Netscape government sales hecker@netscape.com http://home.netscape.com/people/hecker/ --------------9D2A253E386C44F78294D163 Content-Type: TEXT/X-VCARD; CHARSET=us-ascii; NAME="vcard.vcf" Content-ID: Content-Description: Card for Seiferth, Justin begin: vcard fn: Justin Seiferth n: Seiferth;Justin org: AFPEO/BA adr: AFPEO/BA;;Rm: 4D317;Pentagon;VA;20330;USA email;internet: seifertj@www.disa.mil title: Bureaucrat tel;work: 703 693-8068 tel;fax: 703 693-8072 x-mozilla-cpt: ;0 x-mozilla-html: TRUE version: 2.1 end: vcard --------------9D2A253E386C44F78294D163--