How we brought HTTPS Everywhere to the cloud (part 1)

What this post added

This post details the server-side implementation of Automatic HTTPS Rewrites to address mixed content issues. It explains the limitations of browser-based solutions and the need for a performant server-side approach. The core technical challenge addressed is efficiently processing the large database of HTTPS Everywhere rulesets. The solution involves using Ragel to compile domain wildcards into a state machine, optimizing for left-side wildcards by reversing the matching order to reduce state explosion and improve compile times. The post also touches upon the need to rewrite HTTP sub-resources to HTTPS, ensuring availability and correct path upgrades.