Add CORS Support to Artifacts Server | Server

Add CORS Support to Artifacts Server

Joe Becher

The CircleCI Artifact server does not have cross-origin resource sharing (CORS) enabled. This greatly hampers the ability to fetch artifacts programmably

Benifits would include:

being able to fetch artifacts for browser extenstions
being able to extend the platform in ways I can't think of right now :D

Source: https://discuss.circleci.com/t/add-cors-support-to-artifacts-server/806

CCI-I-1018

May 2, 2019

Alex Bakanov

We have same issue with Allure Reports now.

Juliane Lehmann

I came here because we have exactly the same problem as the poster above: can't read the swagger-ui artifacts anymore.

hage vvashi

I hope this too.Recent change (https://support.circleci.com/hc/en-us/articles/360046342233-Artifact-Redirects-Changes) affects our product lifecycle(e.g. api spec review using swagger-ui on Artifacts).Until then, html and other files have the same origin, but now, assets other than html have another origin because the request against those assets will be redirected to the url that have different origin.So I hope that the response from the origin(redirected to) has "Access-Control-Allow-Origin".