Tips: When you see this prompt, it means that the current article has been migrated from the original emlog blog system. The publication time of the article is too long ago, and the formatting and content may not be complete. Please understand.
Formally start the journey of full-site HTTPS encryption
Date: 2017-7-14 Ajue Talks and Chats Views: 2158 times Comments: 0
After a period of internal testing, the blog officially starts the full-site HTTPS.
It has been almost a year since the establishment of the website. I have always wanted to implement HTTPS, but the original host does not support SSL certificates, so it was not possible.
Recently, the hosting service is about to expire, so I switched to a supporting server.
Previously, many people told me that the blog was occasionally inaccessible. I don't know how the upgrade to a better server this time has improved the speed and stability.
Then, my emlog version was also upgraded. Although it is only a test version of 6.0.0, the backend management interface is much nicer than the previous 5.X versions, still using the Bootstrap UI library.
(Note: The following image is the backend management interface of emlog 6.0.0 test version. The settings interface for third-party templates is missing. The template management in the upper right corner of the image was added by myself.)
2. The microblog is gone
When I added the microblog to emlog, I felt it was unnecessary and it was done very roughly. But after everyone got used to it, it was removed again, which is a bit...
Actually, this can also be done with third-party plugins for those who need it. I don't post microblogs much anyway.
Lazy
), so I abandoned it.
Of course, it is very troublesome to achieve full-site HTTPS. Why did I upgrade emlog? The reason is here. Only versions after 6.0.0 fully support HTTPS. If you use previous versions, it would be a nightmare to make the necessary changes...
Besides emlog, the front-end template I am currently using also does not support HTTPS.
The main issue with the front-end template not supporting HTTPS is the Baidu sharing function. It uses HTTP on the article page, causing a mix of HTTP and HTTPS, and the cute little green lock disappears.
"Baidu Share has probably not been updated for two or three years so far. The official website's information is still stuck in 2012. This long period without updates has caused many Baidu products to support HTTPS, but Baidu Share still does not. This is troublesome for developers. If the website has enabled full-site HTTPS, there will be loading issues after using Baidu Share, and the core JavaScript of Baidu Share will be blocked."
I found that someone has already solved this problem online, so we can just be a freeloader.
Github address: https://github.com/hrwhisper/baiduShare
3. The mobile version of the default template has been removed ( It's ugly anyway ), and the current template is responsive, so it is not needed.