For enhanced security and compliance, your JFrog Platform only supports clients that support 302 HTTP redirects for various package types, when working with JFrog Cloud.
This is due to the fact that download requests using clients that don't support 302 redirects will fail in most instances when using the following package types: Bower, Composer, Conan, Cran, Debian, Docker, Git LFS, Gradle, Helm, Maven, npm, PyPI, RPM, Vagrant, and generic.
An example use case of an outdated client not supporting HTTP redirects can be found HERE.
Approved clients
For your reference, the following list of client versions have been tested on the JFrog Platform and verified for 302 HTTP redirect support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: Some older client versions may also support 302 HTTP redirects, however, it is best practice to use the verified versions above.