-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/blog, x/tour, x/talks: {blog,tour,talks}.golang.org are missing redirect from HTTP to HTTPS #42281
Comments
Thanks for the report. I've checked and this applies to {blog,talks}.golang.org as well. All 3 are hosted on App Engine. This is a matter of configuring their respective app.yaml to set CC @golang/release, @golang/security. |
Change https://golang.org/cl/266737 mentions this issue: |
Change https://golang.org/cl/266817 mentions this issue: |
Change https://golang.org/cl/266837 mentions this issue: |
Set secure to always on all handlers so that HTTP traffic is redirected to an HTTPS URL with the same path. References: • https://cloud.google.com/appengine/docs/standard/go/application-security#https_requests • https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_secure For golang/go#42281. Change-Id: I2b86928d51d4e692d29ded1b244f3866c9b087e9 Reviewed-on: https://go-review.googlesource.com/c/blog/+/266737 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
Set secure to always on all handlers so that HTTP traffic is redirected to an HTTPS URL with the same path. References: • https://cloud.google.com/appengine/docs/standard/go/application-security#https_requests • https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_secure For golang/go#42281. Change-Id: Ic03e01d5858e1e5b8ae1b523ab34d970e1403ce0 Reviewed-on: https://go-review.googlesource.com/c/tour/+/266817 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
Set secure to always on all handlers so that HTTP traffic is redirected to an HTTPS URL with the same path. References: • https://cloud.google.com/appengine/docs/standard/go/application-security#https_requests • https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_secure For golang/go#42281. Change-Id: Id89fbcfe97df255173e87f0af4ec71f5238897dc Reviewed-on: https://go-review.googlesource.com/c/talks/+/266837 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
This is fixed now. |
Set secure to always on all handlers so that HTTP traffic is redirected to an HTTPS URL with the same path. References: • https://cloud.google.com/appengine/docs/standard/go/application-security#https_requests • https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_secure For golang/go#42281. Change-Id: I2b86928d51d4e692d29ded1b244f3866c9b087e9 Reviewed-on: https://go-review.googlesource.com/c/blog/+/266737 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> X-Blog-Commit: da7da4462ca59a3ef64f17cd35d619fcf1d3c879
Set secure to always on all handlers so that HTTP traffic is redirected to an HTTPS URL with the same path. References: • https://cloud.google.com/appengine/docs/standard/go/application-security#https_requests • https://cloud.google.com/appengine/docs/standard/go/config/appref#handlers_secure For golang/go#42281. Change-Id: Ic03e01d5858e1e5b8ae1b523ab34d970e1403ce0 Reviewed-on: https://go-review.googlesource.com/c/tour/+/266817 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> X-Tour-Commit: 59417492f03e0d55e544815ff163973cef919f67
When accessing
http://golang.org
, a redirect to HTTPS is made:When doing the same with
http://tour.golang.org
, no such redirect is happening:On top of that, the website doesn't actually work when served via HTTP - it's blank and various errors are logged:
This isn't a problem for browsers which support HSTS Preloading - but for browsers/libraries which don't, this means the website will be broken (and not redirect to the proper HTTPS variant).
This can be reproduced in Firefox by starting it with a new profile (e.g.
mkdir /tmp/ffprofile; firefox --profile /tmp/ffprofile
),opening
about:config
, settingnetwork.stricttransportsecurity.preloadlist
to false and then visiting tour.golang.org.The text was updated successfully, but these errors were encountered: