Branded URLs are easy to implement unless SSL is required. We wanted to provide our customers with an easy solution that will work with our existing clicks solution, requiring minimum effort from them to implement, all while not changing our existing architecture and system.
Our customers need branded URLs in order to maintain their brand equity, improved security practices, and increase click-through rates. In a world where becoming secure is mission-critical, HTTPS is a must.
However, there really is no out of the box solution for apply HTTPS at scale, so we found ourselves having to build our own solution.
In order to implement SSL for our customers, a complicated security process was required involving different groups within the organizations both on the client’s side, and within our own company.
This talk will dive into how we solved this problem with Letsencrypt, Docker, Redis, Nginx, resty-Lua and and autossl module.
42. ● 85,167,054 SSL certificates on the entire internet
(Source: BuiltWith)
● 84.2% of pages loaded in Chrome, on all platforms, are
over HTTPS (Source: Google’s Transparency Report)
● 70.8% of the unencrypted user traffic to Google comes
from mobile devices.
SSL usage