im sory… i mean don’t use it in all pages because the file will become bigger because it will be encrypted in server side. so all the information that you send is not the normal way you type it in. IMO this will be multiplied in random chars to protect your information.
this also helps your website to provide a good market…they will see that their info is safe. :loveblush:
The main reason that I don’t recommend putting your entire site under https is because you may run in to incompatibility with third-party scripts used in your HTML.
That brings up another suggestion: leave the third-party scripts and traffic trackers off the secure checkout pages on your site if possible. You never know when the third-party provider is going to make a change on their end that causes a security warning on your site.
You can pull Google Analytics off of an HTTPS connection. It wouldn’t really be much good to eCommerce if you could not analyze your checkout process.
To actually add to the thread, another time you need an HTTPS connection is when you redirect from a page that is HTTPS to a page that is normally HTTP. In some (or most) browsers doing an HTTPS to HTTP redirection will throw a security warning, for good reason.
And another time, similar, would be a typically non-secure form that shows up on a secure page, if you POST to the non-secure URL, some browsers will warn about Posting secure data to an insecure URL. A typical example of this would be a site quick search that appears on every page; well if it also appears on secure pages, then to avoid browser warnings you should POST that to a secure URL, even though the search form isn’t going to contain any sensitive data.