Reassurances for someone who doesn't understand how SSL work

[GaryKyle]

Hi Mario,

I was just thinking that when I arrive at Gixen, the page I log in at is using h.t.t.p, and h.t.t.p.s doesn't kick in until *after* I'm logged in. However, where I'm used to seeing h.t.t.p.s, like when processing credit card details, I'm used to seeing h.t.t.p.s *before* I submit my information, i.e. on the form I'm filling in my details on. Can you just give me a little overview on how it works so I can reassure myself that my login info is encrypted when sent to Gixen?

Thanks, and apologies if this is a daft question!

Oh, and excuse the dots - aichteeteepee is a banned word

[Cupid]

You are of course correct in your observation as to how other sites present their pages.

However, gixen is secure in this respect because it is the 'target' page that is significant for the encription to take place before transport to the server... and the target page when you press the 'Log in Now' button is an https page... you are then assiged a session id by gixen and redirected to the snipes page, which once again isn't an https page.

If you use Internet Explorer (IE) you can see this process as the little lock appears at the bottom of the window when you press the 'Log in Now' button, for a short time before you are redirected... I'm not sure how it manifests in other browsers though.
_________________
Mark

[nochkin]

GaryKyle,
to finalize Cupid's words..
Secure page is the page which accepts your data when you click "Submit". The page you type your information is not getting transferred while you typing so it's not needed to be secured.

[mario]

By the way, all this has been explained at least couple of times before in the forum. Rest sure your password is always sent over SSL.

[Gixen]