This repository was archived by the owner on Jan 16, 2021. It is now read-only.
Make godoc.org HTTPS-only #304
Labels
Comments
|
Had I noticed a few days earlier I could've filed a nicely self-referential issue there... |
|
Sounds like a good idea. |
Haha, just got it. 😀 |
|
We'd want to set up HSTS in the SSL cert also. |
|
Should be pretty easy to do the server-side part of this with a change similar to this one: golang/tools@40b1b21#diff-871153e4ac7a351c1a6c61e5013b51c8R36 |
jmhodges
added a commit
to jmhodges/gddo
that referenced
this issue
Sep 25, 2015
Redirect HTTP links to HTTPS and set HSTS correctly. Provides command-line flags to help out installations running on non-standard ports and default appengine correctly. Fixes golang#304.
Merged
jmhodges
added a commit
to jmhodges/gddo
that referenced
this issue
Sep 25, 2015
Redirect HTTP links to HTTPS and set HSTS correctly. Provides command-line flags to help out installations running on non-standard ports and default appengine correctly. Fixes golang#304.
jmhodges
added a commit
to jmhodges/gddo
that referenced
this issue
Sep 25, 2015
Redirect HTTP links to HTTPS and set HSTS correctly. Fixes golang#304.
jmhodges
added a commit
to jmhodges/gddo
that referenced
this issue
Sep 25, 2015
Redirect HTTP links to HTTPS and set HSTS correctly. This is specific to the godoc.org set up (with nginx passing a X-Scheme header back) and without fixing up api.godoc.org. Fixes golang#304.
jmhodges
added a commit
to jmhodges/gddo
that referenced
this issue
Sep 25, 2015
Redirect HTTP links to HTTPS and set HSTS correctly. This is specific to the godoc.org set up (with nginx passing a X-Scheme header back) and without fixing up api.godoc.org. Fixes golang#304.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a reason why http://godoc.org doesn't 301 to the https version? SSL is set up and works perfectly, seems like an easy fix.
The text was updated successfully, but these errors were encountered: