Force HTTPS on Heroku

by Miloš Krsmanović • 15.06.2018

Recently I deployed an app to Heroku and I wanted to force my users to only access it over HTTPS. I tried finding a configuration option in the Heroku dashboard but found nothing, then I stumbled upon this help page and the following sentence: “Redirects need to be performed at the application level as the Heroku router does not provide this functionality. You should code the redirect logic into your application”.

This does not agree with this RFC which says “A server MAY indicate that a client request can not be completed without TLS using the “426 Upgrade Required” status code, which MUST include an an Upgrade header field specifying the token of the required TLS version”. Which would mean that the server to requests made using HTTP should respond with:

HTTP/1.1 426 Upgrade Required
Upgrade: TLS/1.0, HTTP/1.1
Connection: Upgrade

Or this RFC that explains the desired behaviour like this: “The server understood the request, but is refusing to fulfill it” and that the server should respond by using the 403 header. Specifically with

403.4 - SSL required

Since the recommendations of the two RFCs are pretty conflicting about what should be the propper way to handle access with non-https and the fact that Heroku is pretty clear with how it expects your app to behave I opted to just redirect the users to the same URL they requested except I then force HTTPS. I wrote a middleware and pluged it in my handler chain before handling any routes. The middleware looks like this:

func forceSSL(next http.Handler) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		if r.Header.Get("X-Forwarded-Proto") != "https" {
			url := url.URL{Scheme: "https", Host: r.Host, Path: r.URL.Path, RawQuery: r.URL.RawQuery}
			http.Redirect(w, r, url.String(), http.StatusTemporaryRedirect)
		next.ServeHTTP(w, r)

You notice that we are using X-Forwarded-Proto to check the originating protocol of the HTTP request. This is because “Under the hood, Heroku router (over)writes the X-Forwarded-Proto and the X-Forwarded-Port request headers” (source).

In a simple application you can use it like this:

package main

import (

func main() {

	http.Handle("/", forceSSL(handler()))

	if err := http.ListenAndServe(":8080", nil); err != nil {

// dummy handler
func handler() http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {

That is it.

This was a simple fix but it allowed me to be sure that my users are accessing my app over HTTPS every time.