"Steve Riley (MCS)" wrote:
>
> I've been doing the same thing, and obviously it does prevent most of the ad
> graphics from downloading. But does it also stop the profiling from
> happening?
>
> If the browser itself sends the URL to Doubleclick, then this solution would
> seem to work. But if the web server you're going to sends the URL instead,
> this this won't work. Chris (Brenton), would verify which of the above
> actually happens?
The connection originates from the user's browser.
Someone else hit on a pretty close approximation to my setup. Basically
you make your local DNS server authoritative for ad.doubleclick.net and
redirect the traffic to a local Web browser. You can then go though the
Web server log extracting all entries with "kw=" but deleting out
entries with "kw=;", "kw=DBCC" and "kw=front". What remains in mostly
search criteria that people have entered at the identified Web sites.
HTH,
Chris
--
**************************************
[EMAIL PROTECTED]
* Multiprotocol Network Design & Troubleshooting
http://www.amazon.com/exec/obidos/ASIN/0782120822/geekspeaknet
* Mastering Network Security
http://www.amazon.com/exec/obidos/ASIN/0782123430/geekspeaknet
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
