For enhanced security and compliance, the new JFrog platform release introduces the removal of support for clients not supporting 302 HTTP redirects on various package types, when working with JFrog Cloud.
Implementing the new standard with the JFrog Platform
Download requests using clients that do not support 302 redirects will fail in most cases for the following list of package types: Docker, Debian, Npm, RPM, Generic, Bower, Composer, Conan, Cran, Git LFS, Gradle, Helm, Maven, Pypi and Vagrant.
To avoid failures, customers should upgrade their clients to a version that supports 302 redirects. See example use case here.
For your reference, the following list of client versions have been tested and verified by JFrog for 302 HTTP redirect support, using the JFrog Platform release.
NOTE: Older client versions may also support 302 redirects, however they have not been officially verified by JFrog. If you are using an older client version, please refer to the client’s release notes for further details.