the situation is such because the one serving the registration form and the one storing the information are from 2 different domains. however, both are pointing to the same database where the user will be logging on in the future. you probably wonder why don't i just get another ssl cert for the domain serving the form, it's not really within my control. the management wanna save some bucks and don't intend to get another ssl cert just for registering member accounts.
Troy Sosamon wrote:
I beleive the answer to your question is yes, the data from the form would be encrypted, but personally I would put the original form on HTTPS at http://domainame.com/register.taf and then post it to https://domainname.com/registerPost.taf.By putting the original form on https, the user will get the paddle lock in the corner while they are filling out the form. Troy Sosamon ===== Original Message from [EMAIL PROTECTED] at 7/02/02 4:40 amhi, the above question has been puzzling me for a while. the situation is this. http://domainname.com/register.taf display a user registration form having [form action="https://domainname.com/register.taf" method="post"] will the data from that page be encrypted when it is sent via https specified in the [form] action? note: the registration form is served from http. could someone enlighten me on this? regards, lance ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
