This is really not the truth:“Any time your browser uses https: it sets up an SSL connection.” Is very easy to simulate a false secured connection. Simply, is possible to show a false https address and keep hidden the true link; also is very easy to show the padlock symbol on a non-secured page. Fishing is based on this tricks. Only the view of html pagesource can say if it is true or not.
About your Firefox problems: I worked to some experiments about and I see that I have your problems only when try to use anonymized proxy servers or “roulette” IP changing. (I hope my words are comprehensibles! Sorry if I write not clearly).
True; should have said “Anytime your browser uses https, it says it is setting up an SSL connection”-of course it could be lying, for the reasons you state.
Hello Technical,
you’ve said that disabling your local proxy did not help. Does this mean, that when you have no proxy in your browser, and WebShield running and redirecting port 80, you can not access your https mails?
thats strange.
Could you please create a packet dump for us? So we can see what’s going on your network?
It’s fairly easy to install (no reboot is needed) and easy to use, just run the program - ethereal, click the first Icon: start the live capture. Then choose you network interface and click OK. Then reproduce the error and the packets will be saved to the log. Save it and mail it to me, please!
thats strange.