[RTFACT-17537] Nuget API v3 feed for remote nuget repositories is not getting updated with the latest index.json of a package Created: 24/Sep/18 Updated: 20/Feb/20 Resolved: 25/Dec/18
|Project:||Artifactory Binary Repository|
|Affects Version/s:||6.1.0, 6.0.1, 6.3.0, 6.3.2, 6.3.3|
|Reporter:||Nihal Reddy Chinna Choudhary||Assignee:||Dudi Morad (Inactive)|
Nuget API v3 feed for remote nuget repositories is not getting updated with the latest index.json of a package. The metadata file for API v3 which is a index.json file is not getting expired in the nuget remote cache. Due to this when there is an update in nuget gallery for a package, the download request for the newer version of the package fails as Artifactory is always giving the index.json of the requested package from the cache.
Issue is reproducible in 6.0.1, 6.1.0 and the latest 6.3.3 version as well.
Steps to Reproduce:
1. Create a Nuget remote repository in Artifactory and set the "metadata retrieval cache period" to 10 seconds to easily reproduce the issue.
2. Request the following metadata file for the "hotchocolate" nuget package using the below URL:
3. The index.json file will be cached in the nuget remote cache in Artifactory.
4. Wait for more than 30 seconds and try to downloading the same index.json for the "hotchocolate" package from the nuget remote cache repo and you will see that the download is successful. The expected behavior is that the request should result in a HTTP 404 message after the metadata is expired based on the metadata retrieval cache setting .
Due to this behavior, if there is a new version of "hotchocolate" package available in nuget.org, the request for this new version would fail as Artifactory keeps giving the index.json that is already cached in the remote repository.
|Comment by Dudi Morad (Inactive) [ 25/Dec/18 ]|
All files under .nuGetV3 folder will be marked as expirable,