I found this signature by analyzing the packets over my ISA box : User-Agent: Windows Live Messenger BETA 8.0.0689 I put it both on Signatures and Headers sections but my clients still can connect to Messenger service and they connect through the same rule on which I've defined those signatures.
Btw the exact signature that I found on the captured packets wasn't just the above statement. The full signature is like this : User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Windows Live Messenger BETA 8.0.0689)
Can it be the reason ? (Not entering the full string)
Edit : I tried the full string, too. No change of attitude.
< Message edited by denizyalcin -- 15.May2006 2:39:38 PM >
Thanks for the fast response. Yes, i just tried putting that string (Messenger BETA), too. Still no difference. Btw when I log the clients who use Live Messenger, I see that some of their Messenger connections happen on SSL protocol. Those SSL connections do go to "omega.contacts.msn.com:443" and "loginnet.passport.com:443". Does the HTTP filtering work on SSL connections ?