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
julieqiu
changed the title
x/pkgsite: doesn't redirect to canonical import path
x/pkgsite: requests do not redirect to when alternative path exists at an earlier version when it was the canonical path
Feb 23, 2021
julieqiu
changed the title
x/pkgsite: requests do not redirect to when alternative path exists at an earlier version when it was the canonical path
x/pkgsite: requests do not redirect when alternative path exists at an earlier version when it was the canonical path
Feb 23, 2021
Thanks @julieqiu. That version did have the canonical import path set to software.sslmate.com/src/go-pkcs12. I assume the redirection is based on the module path in go.mod rather than the canonical import path? In any case I'm glad a fix is planned.
I assume the redirection is based on the module path in go.mod rather than the canonical import path?
Yup that is correct.
I think it makes sense to support custom import paths in addition to redirecting based on the go.mod path.
julieqiu
changed the title
x/pkgsite: requests do not redirect when alternative path exists at an earlier version when it was the canonical path
x/pkgsite: redirect based on custom import paths
Feb 23, 2021
What is the URL of the page with the issue?
https://pkg.go.dev/github.com/SSLMate/go-pkcs12
What is your user agent?
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Screenshot
What did you do?
Navigated to https://pkg.go.dev/github.com/SSLMate/go-pkcs12
What did you expect to see?
Be redirected to the documentation for
software.sslmate.com/src/go-pkcs12
as this is the canonical import path for the package: https://github.com/SSLMate/go-pkcs12/blob/master/pkcs12.go#L18godoc.org exhibited the expected behavior.
What did you see instead?
I saw documentation for the package
github.com/SSLMate/go-pkcs12
, even though this is not the canonical import path.The text was updated successfully, but these errors were encountered: