We’ve updated the way Content Hub identifies itself when fetching files via web links to help ensure your traffic is recognized and not blocked by firewalls. You can now identify these requests using a dedicated user-agent header: ContentHub/10.x.
This header is intended to help identify traffic for publicly accessible files. By configuring your web server or firewall to recognize this header, you can help prevent legitimate Content Hub fetch requests from being flagged as suspicious traffic from cloud providers.