banner
阿珏酱

阿珏酱

いつもとは逆の電車に乗り、見たこともない風景を見に行く
twitter
github
facebook
bilibili
zhihu
steam_profiles
youtube

Officially starting the journey of full-site HTTPS encryption

Tips: When you see this prompt, it indicates that the current article has been migrated from the original emlog blog system. The publication date of the article is quite old, and the arrangement and content may not be complete. Please understand.

Officially Starting the Journey of Full Site HTTPS Encryption

Date: 2017-7-14 A Jue Chatting and Discussing Views: 2158 Comments: 0

image
After a period of internal testing, the blog has officially launched full site HTTPS.

It has been almost a year since the site was established, and I have always wanted to implement HTTPS, but the original host did not support SSL certificates, so there was nothing I could do.
Recently, the hosting was about to expire, so I switched to a server that supports it.
Previously, people often told me that the blog was sometimes inaccessible. I wonder how the speed and stability are with this upgraded server.
I also upgraded my emlog version. Although it is just a 6.0.0 beta version, it looks much better than the previous 5.X version's backend management interface, still using the Bootstrap UI library.
(Note: The image below shows the emlog 6.0.0 beta backend management interface. The settings interface for third-party templates is gone, and the template management in the upper right corner of the image is something I added myself.)
image
2. The microblogging feature is gone.

When emlog introduced microblogging, I felt it was unnecessary and quite rough, but after everyone got used to it, it was removed, which seems a bit...
Actually, this can also be written using third-party plugins, so those who need it can tinker with it... Anyway, I don't post microblogs much ( lazy ), so I just discarded it.



Of course, achieving full site HTTPS is still quite troublesome. Why did I upgrade emlog? The reason is here: only versions after 6.0.0 fully support HTTPS. If I used the previous version, wouldn't that be a hassle...
image

Besides emlog, the current front-end template I am using also does not support HTTPS.

In fact, the main reason the front-end does not support HTTPS is because of Baidu's sharing feature. Using Baidu share on article pages leads to mixed HTTP and HTTPS, causing the cute little green lock to disappear.

"Baidu share has probably not been updated for two or three years now, and the information on its official website is still stuck in 2012. It has been so long without updates that many products in the Baidu ecosystem have become HTTPS compliant, yet Baidu share still does not support it, which is very troublesome for developers. If the site has enabled full site HTTPS, using Baidu share will cause loading issues, as the core JavaScript of Baidu share will be blocked."

After searching online, I found that someone has already addressed this issue, so we can just take advantage of their work.
Github address: https://github.com/hrwhisper/baiduShare

3. The mobile version of the default template has been removed ( anyway, it was very ugly ), and currently, the template is responsive, so it is not needed.


Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.