[S] Videos at IMDb

[JJoe]

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  but isn't the "or" exclusive, meaning that if doubleclick triggers the adpath exception then the jslink can't be disabled. It has to do one OR the other. If not, I'm misunderstanding "or"

Correct. I did not see a need for doubleclick to trigger the jslink exception. Had I, I could have added $SET(0=a_jslink.) to both sides of the "OR" or placed it before the "OR group".

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  

JJoe Wrote:  $OHDR allows access to the request's outgoing headers, http://www.proxomitron.info/45/help/Matc....html#OHDR . In this case, requests to ad.doubleclick.net/ will be allowed when the referer matches http://www.imdb.com/images/a/ifb/doubleclick/expand.html*.

Hmmmm. What's happening seems similar to the model from above, so after learing about that, my thought would have been to use something like this:

Code:

ad.doubleclick.net/(www.imdb.com/$SET(1=adurl_h:0.))

This would match URLs that begin with ad.doubleclick.net/www.imdb.com/. I don't remember the URLs that were requested.

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  I guess I still don't get why headers need to be specified or how that would be evident when figuring out how to construct this exception.

ad.doubleclick.net/ $OHDR(referer:http://www.imdb.com/images/a/ifb/doubleclick/expand.html*)
would match URLs that begin ad.doubleclick.net/ AND have been requested from URLs that begin www.imdb.com/images/a/ifb/doubleclick/expand.html
Assuming that the referer header is available.

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  Is the difference between the two examples above that one involves an imdb path and the other is called from within an imdb html page? I had wondered at times if it were possible to include or exclude a url only in the circumstance where it is associated with another site but hadn't gotten beyond a hazy conception of how the association would matter.

Yes

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  Another thought... If Block Ad URLs was previously not blocking anything, it would seem that inactivating the adpaths/adhosts doubleclick entry would leave a user no worse off than before. I mean, with Block Ad URLs inactive, it's offering zero protection from the sites listed in adhosts/adpaths. Or does activating it somehow deactivate other filters?

Consider "Content-Type: 6a Block Ad Scripts 09.07.04 [sd] (d.2 l.3) (In)". Search the cfg for "adpath:".

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  I've considered just deleting everything in adpaths & adhosts that I've not personally added since sidki's default config doesn't use them anyway

Search the cfg for $LST(adpaths) and $LST(adhosts).
But you could add your entries to Exception-U and use the default config.

(Jul. 04, 2011 01:32 AM)zoltan Wrote:  I suppose it depends on what a user expects from the program.

I think expectations and knowledge. Confirmation does seem reasonable, especially if opt-out or in were included, but maybe only for known problems.