Hi roland, I played with my squid today and found that if you enabled the intercept you shouldn't redirect port 443 to squid, redirect only port 80. So you shouldn't also redirect another secured port used by WLM. I think its a man in the middle attack related. But if you don't activate intercept setting and use proxy setting on client machine, there's no problem at all with WLM. On 16/12/2011 17:27, Roland RoLaNd wrote: > Thanks for your advice. > though that's the page i followed to add destinations to allow. > they're already set in the config and a rule to allow to CONNECT to port 443 and 1863 already exists. > > Some users are able to sign in, others cannot. > and no "deny" hit is showing in access.log so i can troubleshoot. > > PS: i tried using AMSN today, i was able to sign in though the contact list couldn't be loaded. even though i can see in access.log a CONNECt to contacts.live.com:443 > as well as another server which hosts my contact list >
begin:vcard fn:Ebed Tang n:Tang;Ebed email;internet:ebedsat@xxxxxxxxx note;quoted-printable:Yahoo Messenger: ebedsat@xxxxxxxxxxx=0D=0A= Windows live messenger: ebedsat@xxxxxxxxxxxxxxx=0D=0A= url:http://www.facebook.com/ebedtang version:2.1 end:vcard
