Always Be Connecting (With HTTPS)

Making sure users connect to the HTTPS secured version of a site is crucial due to search engines marking down non-HTTPS sites and users adopting tools for more secure browsing. Fly automatically upgrades connections to HTTPS when creating an app, but when using custom domains with self-provided certificates, developers need to upgrade HTTP connections manually. This can be done by detecting the protocol used in incoming connections through headers like X-Forwarded-Proto and redirecting non-HTTPS connections to their HTTPS equivalents. Examples of how to implement this are provided for Go, Node (and Express), and other applications. Automating this process is being considered by Fly but has not been implemented yet.

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.