Avoid permanent redirect to current version

[mlocati]

When browsing to the URL of a package on powershellgallery.com, the server returns a 301 Moved Permanently redirect to the latest version:

C:\>curl -I https://www.powershellgallery.com/packages/PhpManager
HTTP/1.1 301 Moved Permanently
Cache-Control: private
Content-Length: 148
Content-Type: text/html; charset=utf-8
Location: /packages/PhpManager/1.21.0.266
Server: Microsoft-IIS/10.0
Content-Security-Policy: frame-ancestors 'none'
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000
Date: Fri, 29 Nov 2019 11:02:19 GMT

That implies that, when a new package version is released, and we browse to the package url again, we are redirected to the previous version (because of the permanent redirect).

What about using a 302 (or 307) redirect instead?

[bormm]

That explains exactly my issue I have. I had to clear my browser cache to get redirected to the latest version, otherwise I got the oldest and already unlisted version, because that was the first one was permanently redirected to.
That is really a big issue as customers will possibly install old and even unlisted versions instead newer one, if they pick the recommended cmdline that installs the old version.
Its also an issue as nobody understands what happens without deeper investigations.

[dahlbyk]

That implies that, when a new package version is released, and we browse to the package url again, we are redirected to the previous version (because of the permanent redirect).

What about using a 302 (or 307) redirect instead?

In addition to browser caching, the 301 is also respected by search engines to show old versions, e.g.

[tcartwright]

I am experiencing this issue as well. Actually found this by googling powershellgallery 301 redirect. My vote goes to using a 302 like Keith Dahlby (@dahlbyk) suggested. Is there a valid reason for using a 301?

[chris-peterson]

just tripped on this when authoring a package (https://www.powershellgallery.com/packages/GitlabCli)

I thought there was an issue with my package publishing as recent pushes didn't seem to update the "current version" in the Version History table:

what's weird is if I search the gallery, "Latest Version" is correct

when I click through, however, I go to https://www.powershellgallery.com/packages/GitlabCli/1.130.0 instead of https://www.powershellgallery.com/packages/GitlabCli/1.134.0

I also can confirm that this impacts SEO, e.g. on google, my package shows a version that's over 100 versions behind (from 2021 instead of 2025)

[CedX]

6 years later... and this issue is still not resolved?!?
I encountered the same problem, and unfortunately wasted a lot of time trying to understand what was going on.