Hello again,

I've been wondering about this for some time and have not managed to find a definitive answer on it ....

Does anyone know (actually know ) if there is a difference between what WLM / MSN / Windows Live site _needs_ to connect to, as opposed to what it may _want_ to connect to?

Currently I have the following in my bypass list as a generic attempt to get it all working, but of course msn ads come through too.

*live.com*
*msn.com*

I don't want to get into having a second config just for when using WLM / MSN / Windows Live site, but is there a 'magic' solution to allow it all to work and minimise undesirable privacy / ads / tracking issues etc?

Thanks for any informed advice,
Lee
England

Hello again,

Maybe nobody knows the answer here?

In case it helps, I've seen this page listing the urls used, and assuming that is still up to date, I've now got this in my bypass list which is very broad :-

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

However, this appears to be allowing ads through, presumably from rad.msn.com although this is in the AdHosts.ptxt list with Sidki's last config.

So, is there a way I can allow what I'm allowing (above) but also not allow anything from rad.msn.com ?
If so, please tell me what/how/where I would do that in Prox.

Thanks a lot,
Lee

Thanks very much z12,
I'll certainly give that a go.

Can I ask, your post implied that this might be a temporary solution. Did you mean it in that way?

By the way, I previously found another post on here from the end of 2007 suggesting the following should work in the bypass list :-

(\w.|)omega.contacts.msn.com[:/]
login.live.com[:/]

However, assuming that is still up to date, it looked like it might be more limited that what I'm trying to do. ie, presumably it just gets the messenger protocol itself more or less functioning through Prox and Sidki's config. My aim of course, is to get all the messenger 'bits' working as well as any associated live.com pages.

As an aside here, why do microsoft's sites such as live.com or Windows Update seem to get broken by Sidki's config? What is unusual or tricky about their design? I'm never very successful when it comes to debugging such issues myself using Prox's log window and then knowing how to use any details I find.

As a further aside, although this warrants its own post or set of posts, my bypass list is becoming increasingly generic, which I don't really like. Below is how it currently is (minus the msn stuff). If anyone reading this recognises what I might be wanting to do and knows a better solution, please free free to enlighten me.
It might be a good idea if you post your kind help in a new thread, so other people can also find your help without it being buried in this one.

local.ptron
*microsoft* - mainly for windows update
*mozilla* - for TB + FF updates and addon updates
*erweiterungen.de* - for a specific Thunderbird addon update
*foxitsoftware* - to allow Foxit Reader to check for updates
*paypal* - mainly because I find otherwise I often get logged out during navigating the site
*ebay* - no specific reasons come to mind now, but I feel the site doesn't like being filtered
*o2* - no specifics come to mind now, but if I use the site filtered, general functionality can be problematic

Hello again z12,

Unfortunately, it appears WLM cannot log in with your 3 lines replacing any previous ones.
The Prox log shows the following, which presumably shows some trouble with login.live.com ?
I have no idea what the slashdot.org referrer is.

*** Log Reset ***
Client opened: total 1
GET 3 : Pragma no-cache stripped

+++GET 3+++
CONNECT / HTTP/1.0
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; IDCRL 4.100.313.1; IDCRL-cfg 4.0.5633.0; App msnmsgr.exe, 8.5.1302.1018, {7108E71A-9926-4FCB-BCC9-9A9D3F32E423})
Host: login.live.com:443
Content-Length: 0
Proxy-Connection: Keep-Alive
Referer: http://slashdot.org/search/referrer-karma.php?q=Big+Bang
+++CLOSE 3+++
Client closed: total 0

Hello again z12,

By WLM I mean Windows Live Messenger.

I've just tried using Minimal Mode and no bypass entries, and WLM will not log in.

I'm never good at understanding how to debug and then make manual bypasses using the Prox debug window.
I think I'll look at the WLM connection log instead and see if I can get anything clearer / simpler from that angle.
I suspect however I'll probably just end up with using the same broad bypass list entries that I've already used.