You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this an oversight? Or is it intentional (e.g., because it's needed for testing, or because it's too hard to redirect those domains)?
Unless there's a good reason for it, they should redirect to https. It's inconvenient and uses up people's time having to manually modify URLs to https form when visiting or sharing/pasting URLs.
The text was updated successfully, but these errors were encountered:
bradfitz
changed the title
http://{tip,beta}.golang.org should redirect to https.
x/tools/cmd/godoc: {tip,beta}.golang.org should redirect to https
Jul 18, 2017
Just wanted to mention that tip.golang.org redirects to https now. I can send a CL to make the change for beta.golang.org also, if somebody can point out where to make that change.
For tip, there is a special x/tools/cmd/tip, I don't see anything like that for beta.golang.org. There is just this comment inside cmd/godoc/autocert.go though.
// TODO: make this the default? We're in the Go 1.8 freeze now, so
// this is too invasive to be default, but we want it for
// https://beta.golang.org/
http://golang.org redirects to https://golang.org (as do blog, tour, etc., subdomains), but http://beta.golang.org and http://tip.golang.org do not redirect to their https equivalent.
Is this an oversight? Or is it intentional (e.g., because it's needed for testing, or because it's too hard to redirect those domains)?
Unless there's a good reason for it, they should redirect to https. It's inconvenient and uses up people's time having to manually modify URLs to https form when visiting or sharing/pasting URLs.
The text was updated successfully, but these errors were encountered: