Something I've been doing over the years now is putting any form information behind https. If a user has to enter any personal information, even their name, I've got that form sitting behind https.
Is there a general best practice guideline for this? I mean, I would think that if a user is typing "anything personal" into a form, https would be appropriate?
Marshall
2:28 pm on Jul 15, 2007 (gmt 0)
What is personal any more? How many sites ask for name, address, phone and DOB just to "register" without being an https form, or encrypted for that matter. Unless it is sensitive informaiton such as social security number, user ID, password, credit card, etc., I personally do not think using http is bad/wrong.
[i]Marshall]/i]
rocknbil
4:38 pm on Jul 29, 2007 (gmt 0)
I agree, identity numbers, SSN, Drivers' license, CC's or anything financial or sensitive, https. Https is significantly slower so it's in the interest of your users you don't use https unless you have to. Also important when you're done is a method of getting off https afterward, otherwise any browsing after completing the submit stays on https, which makes your site look very slow.
rshosting
9:30 am on Aug 3, 2007 (gmt 0)
Its really not necessary to have https for all forms.
The forms were on which client put there CC details or something similar need https access for security reason.