Affects Version/s: 6.5.3
Fix Version/s: None
When setting up a generic remote repository to proxy a generic local repository from another instance, the file uploaded to generic local repository named "test" twice, each time with a different content causing it to overwrite and change the checksum, the file downloaded again in the generic remote to the generic remote cache will not be the same as the new one added in the generic local. The checksum will be of the old file.
The only way to update the generic remote cache with the new file is to delete it from the generic remote cache.
Steps to reproduce:
1 - Setup a generic local on Artifactory1
2 - Setup a smart generic remote on Artifactory2
3 - Upload a file named "test" with checksum=xxxxxx
4 - Download the file from generic remote to cache it as "test" and checksum=xxxxxx
5 - Change the content of file "test" and upload it to generic local on Artifactory1, so now the checksum=yyyyy
6 - Use Zap cache with all configuration set to zero in the generic remote, so the file will be downloaded from remote and there is no cache.
7 - Click on the file in the UI for download and refresh the generic remote cache repository and notice that the checksum is still checksum=xxxxxx and was not updated to checksum=yyyyy.
The file will be updated in the cache upon download from the generic remote, only if you delete the old one that is holding the same name.