Code Forums - View Single Post

technobard · 01-27-2005, 11:34 AM

I think I get it. BankOne does the same thing. There is a way to go straight to an HTTPS form, before entering the user/pass, but I agree I don't think there's a problem. When you type your user/pass, the info isn't sent until you POST. The form action (<form name="loginForm" method="POST" action="https://global1.onlinebank.com/cgi-forte/forteisapi.dll?ServiceName=WebTeller&TemplateName= WebTeller.htm&BankTag=firstreg0101" target="_top">) is to a secure URL. So when you actually transmit the info, you're fine. Right?

Having said that, I'm still more comfortable being in an HTTPS page to start with. On the link you provided, go to "Home Banking" on the menu, and select "Access Your Account". It will take you to an HTTPS form. I do the same thing with my bank.

01-27-2005, 11:34 AM	#5 (permalink)
technobard Centurion Nova Prime Join Date: May 2002 Location: Oak Park, IL (USA) Posts: 287	I think I get it. BankOne does the same thing. There is a way to go straight to an HTTPS form, before entering the user/pass, but I agree I don't think there's a problem. When you type your user/pass, the info isn't sent until you POST. The form action (<form name="loginForm" method="POST" action="https://global1.onlinebank.com/cgi-forte/forteisapi.dll?ServiceName=WebTeller&TemplateName= WebTeller.htm&BankTag=firstreg0101" target="_top">) is to a secure URL. So when you actually transmit the info, you're fine. Right? Having said that, I'm still more comfortable being in an HTTPS page to start with. On the link you provided, go to "Home Banking" on the menu, and select "Access Your Account". It will take you to an HTTPS form. I do the same thing with my bank. __________________ It takes 2 points to draw a straight line, but at least 3 points to draw a conclusion.