The company has developed an e-mall project. Now requires registration, login, shopping cart, payment these pages are set to HTTPS transmission, other pages for HTTP transmission. Ask Master how to configure?
Reply content:
The company has developed an e-mall project. Now requires registration, login, shopping cart, payment these pages are set to HTTPS transmission, other pages for HTTP transmission. Ask Master how to configure?
A single domain name does not solve this problem, because when you exapmle.com
deploy the site https
, the entire site is https
transmitted,
You can select the appropriate transport mode for a site
General Page http://example.com
Login Registration Https://account.example.com
Shopping Cart https://cart.example.com
Payment https://pay.example.com
Deploy two domain names: http://a.com and https://ssl.a.com, the relevant places can be cross-domain.
Agree with @leandre and @godruoyi answer, the need to use the HTTPS protocol domain name alone, request the relevant URL when the HTTPS protocol.
However, there is an inconvenient place: usually a HTTPS protocol domain name of the page, the need to access the HTTP protocol domain name content, so that involves cross-domain issues, cross-domain also has a related solution, can do, just can be troublesome.
So it is recommended that the whole station with HTTPS, although performance will be lost, but the optimization done well, HTTPS performance is fully acceptable.