For some unknown reason, apache.jfrog.io issues redirects.

• The GET.sh script is not able to follow these location headers.
• apt-cacher-ng cannot follow these locations, as they are https and hence CONNECT is used

Following solutions come into my mind:

Do the redirects in GET.sh

The headers are known before talking back to apt-cacher-ng. Hence Location requests can be parsed and followed by the GET.sh script by looping.

Downside: We must be able to grok what we are doing there

Downgrade https redirects

Downgrading https:// to http:// should work, too. In that case apt-cacher-ng issues a new request with the http: destination.

However in that case the destination must be known to the script to upgrade to https:// again. There are possibly many such destinations. Hence some automation should be added to recognize the downgraded destinations for upgrade again.