In order to improve the performance of our artifacts hosting, we are trialling an upcoming change to 302 redirect non-HTML artifact downloads directly to a short-lived pre-signed S3 URL.
Over the coming days we will be doing a staged percentage-based rollout of this feature, and listening for your feedback. We hope you will be pleased with the results.
If using a web browser (to view HTML resources such as test / coverage reports or download tarballs / zip files) you will not need to change your behaviour, as browsers follow redirects by default.
However, if you are using
curl or another HTTP client that does not follow redirects by default, you will need to enable redirect support (
wget follows redirects by default, while
curl requires the
An example with
curl might be:
$ curl -H'Circle-Token: XXXXXX' 'https://9648-63890343-gh.circle-artifacts.com/0/sample/logs.txt' Redirecting to <https://circle-production-customer-artifacts.s3.amazonaws.com/picard/5791283ac9e77c000185fe90/5e539f5568af022586ab1ffe-0-build/artifacts/sample/logs.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20200227T162059Z&X-Amz-SignedHeaders=host&X-Amz-Expires=59&X-Amz-Credential=XXXXXXXXX%2F20200227%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=XXXXX>
$ curl -L -H'Circle-Token: XXXXXX' 'https://9648-63890343-gh.circle-artifacts.com/0/sample/logs.txt' some logs...... some logs...... some logs......