When viewing CircleCI artifacts of a HTML page I am getting a slew of errors like:
Access to font at 'https://circle-production-customer-artifacts.s3.amazonaws.com/picard/forks/5630d993ae796b0b2be8a441/160366670/GuillaumeFavelier/mne-python/5eb15a16258f2e1cf28f63d1-0-build/artifacts/dev/_static/fonts/source_sans_pro/TTF/SourceSansPro-Light.ttf' from origin 'https://19884-1301584-gh.circle-artifacts.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
See for example this artifact. This is something new in the last week or two, though it appears to affect looking at artifacts from at least 25 days ago, so I’m guessing it’s due to some AWS artifacts reconfiguration?
Hiya @Eric89GXL - it looks like this is directly due to our recent change with redirecting artifacts: https://circleci.com/changelog/#artifacts-redirects. We recently rolled out a change that allowed JSON files through CORS, but it looks like there are some other file types we should consider allowing through. I’ll pass this along internally, and cross-post this to the GitHub discussion for visibility
@gmemstr I’m having similar issues with redirects when trying to fetch an svg. Could svg files also be whitelisted? Or is there a way to disable the redirect?
