We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://pkg.go.dev/github.com/google/go-containerregistry@v0.4.1/pkg/v1/
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150 Safari/537.36
I added a trailing / to the URL https://pkg.go.dev/github.com/google/go-containerregistry@v0.4.1/pkg/v1
/
I expected to see it succeed and show documentation.
400 Bad Request
This seems potentially related to #43979, at least insofar as it's another bug with handling trailing slashes.
In general it's probably fine to just remove trailing slashes and handle the request the same, or even just redirect to the trailing-slashless URL
These both work:
This doesn't:
So it seems like it's specific to handling sub-packages in a module where the version is included in the URL.
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/301869 mentions this issue: internal/frontend: fix 400 due to trailing slash
internal/frontend: fix 400 due to trailing slash
Sorry, something went wrong.
golang/pkgsite@bc9224e
No branches or pull requests
What is the URL of the page with the issue?
https://pkg.go.dev/github.com/google/go-containerregistry@v0.4.1/pkg/v1/
What is your user agent?
Screenshot
What did you do?
I added a trailing
/
to the URL https://pkg.go.dev/github.com/google/go-containerregistry@v0.4.1/pkg/v1What did you expect to see?
I expected to see it succeed and show documentation.
What did you see instead?
400 Bad Request
This seems potentially related to #43979, at least insofar as it's another bug with handling trailing slashes.
In general it's probably fine to just remove trailing slashes and handle the request the same, or even just redirect to the trailing-slashless URL
These both work:
This doesn't:
So it seems like it's specific to handling sub-packages in a module where the version is included in the URL.
The text was updated successfully, but these errors were encountered: