Automatic HTTP redirect is 301 - can we change it or add headers?

[gurubobnz (Bob Brown)]

Hi all,

We are using Caddy’s automatic HTTPS support as follows:

website.com {
    tls my@email.com
    proxy / localhost:8080
}

Our production setup is more complex, but this is the essence of it. This works fine, but the automatic redirection sends a 301 redirect which we’d like a little more control over. Specifically:

• Would like to specify a 302 instead of a 301
• Would like to add Cache-Control headers to limit the time that 301’s are cached in Chrome or Firefox (http://stackoverflow.com/questions/9130422/how-long-do-browsers-cache-http-301s)

The documentation is not clear on this point and I couldn’t find where in the source this magic happens. Does anyone have any suggestions?

Cheers,

- Bob -

[gurubobnz (Bob Brown)]

I think I found the line of code that is responsible for the 301 redirect - seems there’s no way for it to be anything other than http.StatusMovedPermanently (301) - https://github.com/mholt/caddy/blob/master/caddyhttp/httpserver/https.go#L153

[Whitestrake (Matthew Fay)]

There aren’t any directives that modify the redirection behaviour of Automatic HTTPS. You should be able to split up your site into two vhosts for fine-grained control of the redirection process, though. It would look something like this:

http://website.com {
    redir / https://website.com{uri} 302 
    header / Cache-Control "max-age=3600"
}

https://website.com {
    tls my@email.com
    proxy / localhost:8080
}

[matt (Matt Holt)]

This is the correct answer.