Skip to content
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/website: Redirect sha256 checksum to #41894

owenthereal opened this issue Oct 9, 2020 · 1 comment

x/website: Redirect sha256 checksum to #41894

owenthereal opened this issue Oct 9, 2020 · 1 comment


Copy link

@owenthereal owenthereal commented Oct 9, 2020

What version of Go are you using (go version)?


Does this issue reproduce with the latest release?


What operating system and processor architecture are you using (go env)?


What did you do?

The download of a Go release redirects to but the download of the same release's sh256 checksum does not.

For example:

$ curl
<a href="">Found</a>.

$ curl
<!DOCTYPE html>
<meta name="go-import" content=" git">
<meta http-equiv="refresh" content="0;
Nothing to see here; <a

The sha256 URL is available at by appending .sha256 to the end of a release:

$ curl

To summarize,

  1. ✔️ curl ->
  2. 🚫 curl -> curl
  3. ✔️ curl
  4. ✔️ curl

What did you expect to see?

It would be nice that a release's sha256 can be redirected from to, the same as its corresponding release. This makes the download of a release and its checksum both accessible from

What did you see instead?

The download of a release's checksum is not possible from the host

@gopherbot gopherbot added this to the Proposal milestone Oct 9, 2020
Copy link

@owenthereal owenthereal commented Oct 9, 2020

I took a stab at supporting this: golang/website#24. PTAL.

@owenthereal owenthereal changed the title proposal: x/website/internal/dl: Redirect sha256 checksum to x/website: Redirect sha256 checksum to Oct 9, 2020
@dmitshur dmitshur self-assigned this Oct 10, 2020
@dmitshur dmitshur removed this from the Proposal milestone Oct 10, 2020
@dmitshur dmitshur added this to the Unreleased milestone Oct 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants