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

HTTP cache: RepositoryResources resource is not cached in a versioned way #7997

Closed
dtivel opened this issue Apr 12, 2019 · 0 comments · Fixed by NuGet/NuGet.Client#2801
Closed

Comments

@dtivel
Copy link
Contributor

dtivel commented Apr 12, 2019

Although RepositorySignatures resources are versioned, the cached content is not versioned in NuGet's HTTP cache.

This means if a 5.0 client populates the cache with a RepositorySignatures/5.0.0 resource where allRepositorySigned is true and then a 4.7-4.9.3 client uses the cached resource, restore will fail like this.

  1. Clear all caches. (nuget locals -clear all)
  2. Restore a package from https://nuget.org using a 5.0 client.
  3. Within 30 minutes, which is how long the HTTP cache is valid, use a 4.9.3 client to restore a different package.

Result: The 4.9.3 client restore will fail like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant