Best practise for "http-redirect" requests in Github (or other redirect szenarios)

Hi community,
at the moment i am dealing with one topic and i would like to ask for best approaches in regards to following szenario with ZIA.

In costumer environment exists servers (and/or other systems) which downloads content from Github. For these downloads the proxy connection should be used.

As an example, for a docker-compose download the following URLs:
https://github.com/docker/compose/releases/download/v2.2.3/docker-compose-linux-x86_64

To filter and to create costum URL categories for constant links are straightforward as of know (either as URL or work with Keywords). However, in this case (or in other circumstances) a ‘http-redirect’ happens (http code 302) and redirect to following Github target:

https://objects.githubusercontent.com/github-production-release-asset-2e65be/15045751/992b9422-bd09-4be4-9c50-27ee8219c1a7?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220119%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220119T14

This behaviour happens, as i have read, also with other Github links.

What are the best approaches in this case, to allow Download for Github (in this example; Traffic for object.usercontent.com) under following circumstances:

  • How do to allow download for docker-compose but not for anything on github?
  • How to allow the redirect target (object.usercontent.com) without whitelisting the whole domain and subsequently allow any further files on object.usercontent.com?

Thanks for your help and ideas in advance,
Christoph