Windows Live Messenger & live.com ; required exceptions

[leecovuk]

Hello everyone,

As you might know, if you use Windows Live Messenger and live.com, they don't work properly through Prox+Sidki (maybe indeed through any other config too).
For some time, I've had the following entries in the bypass list, but I don't think I've ever had it set ideally; specifically regarding how to filter (or block?) rad.msn.com whilst still allowing other bits of msn.com. rad.msn.com seems to deliver the ads in Messenger, some of which are very intrusive including on-mouse-over 'popouts'.

*live.*
*.hotmail.*
*.msn.*

(Note: login.live.com may be sufficient as an exception just for Messenger, but various parts of live.com itself break through Prox+Sidki)

I based the above on looking at this page :-

Network ports and urls required for Windows Live Messenger 2009, by Microsoft

Can anyone suggest a better/correct/more efficient set of bypass or exception entries, for both Windows Live Messenger and live.com?
(whilst still trying to tame ad delivery from rad.msn.com)

Thanks for any wisdom,
Lee

[lnminente]

Messenger tries to do a secure connection on port 443, try one thing, disable the filtering of secure pages and try again. If problem persists take a look to the log window to see if proxo is blocking some URL.

============================
My own filter to clean-up messenger is the following (with SSL filtering disabled), if someone adapt it to Sidki's config please post it here too.

Code:

[HTTP headers]
In = TRUE
Out = FALSE
Key = "! :I_52 Kill garbage in MSN messenger {ln}090506 TEST"
URL = "(^local.ptron)(^$TST(keyword=*.NoKill.*))"
Match = "(^$URL(http://config.messenger.msn.com/*))$TST(UserAgent=Mozilla/*; Windows Live Messenger*)$SET(9=$GET(UserAgent))  $ADDLST(Log2,I_Kill garbage in MSN messenger\t$DTM(Y/M/D H:m:s't) ($DTM(c))\t$GET(uDom)\t$GET(uExt)\t$GET(ContentType)\t$GET(Resp)\t$GET(ContentLength)\t\u\t((^$TST(\9=*))~|\9)\t\4\t$GET(Referer))"
Replace = "$LOG(RHeader $DTM(c),I_3.00 Kill garbage in MSN messenger: \u) $JUMP(http://local.ptron/base/killed.html?WHY=$ESC(Kill garbage in MSN messenger)&URL=$ESC(\u))"

[leecovuk]

(May. 20, 2009 05:40 PM)lnminente Wrote:  Messenger tries to do a secure connection on port 443, try one thing, disable the filtering of secure pages and try again. If problem persists take a look to the log window to see if proxo is blocking some URL.

Hello Inminente and thanks for your reply.

To clarify, do you mean I should disable filtering of secure pages whilst keeping my current bypass list entries? Or do you mean remove/comment out my bypass list entries first?

Lee

[lnminente]

In my own config when i had enabled SSL filtering, messenger couldn't connect because the certify was not valid. To find the problem i suggest to don't bypass the urls and try disabling secure filtering, if you can connect, then we will know more accurately if it is the problem or not.

Sidki's config also uses half-ssl, i THINK this concept are some redirections to convert secure connections to normal between proxomitron and the browser/messenger. Don't know more about it, hope it helps you in anything.

[leecovuk]

Hello again,

I find I can now indeed log into Messenger, with secure page filtering disabled in Prox's config and without my bypass list entries.
I can't yet fully test all Messenger functionality, as I currently have no contacts online.

Assuming this change is all that is needed (which it may not be), how do I allow Prox to generally filter secure pages but set up an exclusion/bypass entry for login.live.com?
IncludeExclude-U.ptxt has an example of :
don't use half-SSL (if default) $SET(0=i_ssl_h:0.)
so I don't know if 'don't filter ssl' would be $SET(0=i_ssl:0.)
eg
*login.live.com* $SET(0=i_ssl:0.)
?

Alternatively, Messenger routes through Internet Explorer's Internet Options doesn't it, (where I use Prox in circuit on http and https), so maybe a simple solution would be to use the general connection settings options there and set:
'don't use proxy server for addresses beginning with'
for
https://login.live.com
?

Lee

[sidki3003]

Lee, try to avoid that initial asterisk for URL matches.

For instance, your *live.* Bypass List entry is also bypassing http://somesite.com/somepath/tracklive.js . Even *login.live.com would still bypass http://somesite.com/trackme?ref=http://login.live.com/this.html .

Now, in case of future problems, no one could help you, because they don't know that you're bypassing a good part of the Web with a couple of those extraordinary expressions.

That final asterisk isn't needed, because URL expressions in lists just need to match the beginning, not the entire URL. In fact, as for the IncludeExclude list it may even cause a loop under certain conditions.

I was trying to explain the URL expression syntax here, a more exhaustive explanation is here. This syntax applies to all URL-type lists, including the general Bypass List.

edit: I didn't mention the syntax for HTTPS though:
Match all secure pages on login.live.com: login.live.com:
Match all secure pages on the entire live.com domain: ([^/]++.|)live.com:

[leecovuk]

ok, thanks Sidki.
I shall as usual, wander away and try to apply your and others' advice.

Lee