The Hardest Working Header on the Internet
Blog post from exe.dev
exe.dev routes web requests to the appropriate virtual machine using the HTTP Host header, a mechanism central to modern web infrastructure such as load balancers, CDNs, and web servers. Users can connect custom domains to their VMs, with Let’s Encrypt certificates provisioned automatically, and can now also configure wildcard certificates such as *.example.com to direct all subdomains to one VM for custom routing. Wildcard domains can be added through the service’s lobby using the “domain add vm-name *.example.com” command, while DNS time-to-live settings may still delay activation; the post also corrects an earlier claim that Certificate Transparency caused such delays.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.