Geek Answers Handbook

Switching from http to https, what problems should I handle?

My site has https (ssl) sections and others have regular http (without using ssl).

Are there any problems with ssl on pages other than ssl?

This user will click on the link several times, which will be ssl, and then click on another link that leaves https on the http addresses.

I understand that on the ssl page, all images must also be sent using https.

What other problems should I handle?

I remember that the pop-up menu sometimes informs the user about a security problem, for example, some content is not protected, I assume that this is when you are under https, and the page loads images that are not under https.

+5
source share
3 answers

The Codeproject has a good article on this topic. The author encapsulates switching by code and configuration. Not so long ago, I tried to go this route - and stopped walking. There were some processing problems. But the main reason for the stop was the poor user experience mentioned by Joel before.

+1
source

Blending is usually a bad idea just because it tends to detract from the user experience and coding around differences, which makes the application much more difficult to maintain. If you need SSL even for a small site, I would recommend putting it under SSL. Some companies use a hybrid for the public "bottom" site and SSL for real customer experience.

, , , . , , .., , sessionid (cookie ).

+2

If you use sessions on your site, you lose session information when switching between ssl pages and non-ssl pages.

0
source

More articles:


All Articles