Do you think it might be possible to block ForeSee Results?

Edit Subject

This obnoxious script fires every second(!), and tries to deposit tracking cookies.

A typical site using ForeSee Results is www.aarp.org, which launches it like this:

<script type="text/javascript" src='/foresee/foresee-trigger.js'></script>

Its home, www.foreseeresults.com, does something similar:

<script type="text/javascript" src="/_surveycode/foresee-trigger.js"></script>

However, some other sites attempt to bury it, e.g.:

http://travel.state.gov/passport/

which brings in

http://travel.state.gov/_res/javascri...

that executes:

document.write('&lt;script type=&quot;text/javascript&quot; src=&quot;/foresee/foresee-trigger.js&quot;&gt;&lt;/script&gt;');

1 person has
this question +1

Answered

CHAMP

0

Edit

Delete

Remove

Official

Fork

Felix Shnir July 08, 2010 20:09

Hey Eric, thanks for using Ghostery.

We'll test foresee for cookie tracking functionality and most likely add definition for it later this or early next week. Thanks!

Comment

good answer! good answer! (undo)
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this question?

Hey Eric, thanks for using Ghostery. We'll test foresee for cookie tracking functionality and most likely add definition for it later this or early next week. Thanks!

How does this make you feel? Add Image

I'm
e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned
Cancel
CHAMP

0

Edit

Delete

Remove

Official

Fork

Eric P. Scott July 29, 2010 21:12

It looks like this one is a little more complicated.

Some sites (e.g. drugstore.com) have a second component [foresee-alive.js], which could presumably be trapped by changing the detection pattern to /foresee-(alive|trigger)\.js/

But then I found some sneaky sites, like shopping.com, that hide ForeSee code in obscure places, e.g.:

homePageBtmOmiFS-all-min.js
searchResultPageBtmOmiFS-all-min.js
singleModelPageBtmOmiFS-all-min.js

Environment:

Ghostery 2.2.1 + Firefox 3.6.8 (Linux)

Privacy Preferences:
[checked] Accept cookies from sites
[unchecked] Accept third-party cookies
Keep until: ask me every time

Comment

good answer! good answer! (undo)
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this question?

<p>It looks like this one is a little more complicated.</p> <p>Some sites (e.g. drugstore.com) have a second component [foresee-alive.js], which could presumably be trapped by changing the detection pattern to <code>/foresee-(alive|trigger)\\.js/</code></p> <p>But then I found some sneaky sites, like shopping.com, that hide ForeSee code in obscure places, e.g.:</p> <blockquote>homePageBtmOmiFS-all-min.js<br />searchResultPageBtmOmiFS-all-min.js<br />singleModelPageBtmOmiFS-all-min.js</blockquote> <p>Environment:</p> <p>Ghostery 2.2.1 + Firefox 3.6.8 (Linux)</p> <p>Privacy Preferences:<br />[checked] Accept cookies from sites<br />[unchecked] Accept third-party cookies<br />Keep until: ask me every time</p>

How does this make you feel? Add Image

I'm
e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned
Cancel
CHAMP

1

Edit

Delete

Remove

Official

Fork

Felix Shnir July 29, 2010 21:49

Hey Peter. From my earlier checking, I was under the impression that once the trigger was blocked, any additional alive calls were not processed. Nonetheless, I've updated the bug definition for it.

The other case is a lot trickier. The only quick way I can think of is using surrogate technique when ForeSee is registered in the DOM, tho this isn't something readily available in Ghostery.

Comment

good answer! good answer! (undo)
- view -1 more comments
- Eric P. Scott July 29, 2010 22:49
  
  I thought that as well. But I still got cookie alerts, and about:cache listed foresee-alive.js. View Source revealed an explicit <SCRIPT> reference.
  
  Thanks for your prompt response!
  
  Edit
  
  Delete
  
  Remove
- Cancel
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this question?

Hey Peter. From my earlier checking, I was under the impression that once the trigger was blocked, any additional alive calls were not processed. Nonetheless, I've updated the bug definition for it. The other case is a lot trickier. The only quick way I can think of is using surrogate technique when ForeSee is registered in the DOM, tho this isn't something readily available in Ghostery.

How does this make you feel? Add Image

I'm
e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned
Cancel

Reply to This Topic (some HTML allowed)
What's the status of this question?

How does this make you feel? Add Image

I'm
e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned

About this Question

Products & Services

Tagged

Do you think it might be possible to block ForeSee Results?

Edit Subject

About this Question

Products & Services

Tagged

Do you think it might be possible to block ForeSee Results? Edit Subject

Do you think it might be possible to block ForeSee Results?

Edit Subject