Need some help with exceptions please....

[ProxoDent]

(Oct. 10, 2009 03:58 AM)JJoe Wrote:  

(Oct. 10, 2009 01:47 AM)ProxoDent Wrote:  - a_adscr. resolved the issues of not being able to read mail, etc.;

This removes the need for the filter but I did see Ad Scripts that it could allow.
Probably prefer another solution.

Yes. I noted 2 additional inline scripts that are allowed as a result (could easily change), but I think at least one of them is an undesired hit just like the 'Loc' code.

The 'Block: Ad Scripts - Content' filter that causes the original issues triggers this code in AdKeys-J.ptxt (as you are aware):

Code:

ad(v[#0:*]|id|s((^rc$TST(\3=>))[b-df-km-z][a-z]+{1,*}|(^=(\=\=|{})))
  |x(^ml)[a-z]+|[#0:*][g-z][a-z]+|_[a-z0-9]+{1,*})

which in turn matches the 'ad' like words in the following snippet from the 'Loc' script (the first match is 'adsMinInterval'):

Code:

"15.1.3020.0910",config : {adsMinInterval: "2", adsMinActions : "1",cookieDomain: ".mail.live.com",imgSvrUrl : "http://gfx2.hotmail.com/mail/w4/pr01/ltr/"}};Page = {addFeedbackData :

Most (if not all, at least that I could see) of the advert content is coming from code that is blocked by other filters, so relaxing the filtering via 'a_adscr' may be okay in this case. However, I probably say that because I'm not smart enough to come up with a filter that strikes the right balance between restricting too much and too little. Perhaps in the case of 'live.com', it might be better to err on the side of being less restrictive so as not to break anything when a single character of code changes.

(Oct. 10, 2009 03:58 AM)JJoe Wrote:  

(Oct. 10, 2009 01:47 AM)ProxoDent Wrote:  and in regard to 'hotmail.com':

I didn't notice a problem. I did see 'Loading ...' tho...
a_js. is broad.

Yep, it is broad. I'm checking in to narrowing it down. By the way, the problem that I am encountering is a 'waiting cursor' while 'Loading' even as the status bar says its 'Done' (see screen-shot for example) and eventually, the loading finally times out with an error message posted to the page (see attached screen-shot). The issue is highly repeatable, though it does not happen every time one attempts to read mail (maybe one out of every three tries or so). The problem goes away after applying the exception.

(Oct. 10, 2009 03:58 AM)JJoe Wrote:  

Code:

[^/]++.live.com/*$SET(0=a_adscr.a_noprint.a_rdlink.$TST(uDom=live.com))
[^/]++.hotmail.com/mail/*$SET(0=a_js.$TST(uDom=live.com))

The * isn't necessary.
I don't think $TST is doing what you think it is doing.
I'd expect $SET to set the variable when executed.
I'd expect $TST inside $SET to affect the variable, not the match.

I agree with all your points. It was also redundant to have a test for 'uDom=live.com' when matching against '[^/]++.live.com' even if it did what I thought it was doing. I got a little hasty there. Just remove the $TSTs from the $SET code (and the asterisks can go as well). I found a couple of additional issues while playing with the site that I will address in the next post, and I'll present the (cleaned up) exceptions again updated for handling the new items.

Thanks.

P.S.

This is mostly academic for me now as I have installed the 'Outlook Connector' to handle most of the Live mail functions in Outlook:

http://www.microsoft.com/downloads/detai...laylang=en

Most customization still requires visiting the Web-based service, though.