v2 API should support CORS request from status page widget

[Darcy Parker]

https://bitbucket.org/atlassian/statuspage-status-widget/src/45e02903fccfea51e0c9f9d1c666a259bb4feb98/src/util/fetch_status.ts#lines-20

makes a GET request to https://someStatusPage.statuspage.io/api/v2/summary.json and the response is not accepted in browsers from a cross origin such as https://localhost:9000 because the API’s response does not have Access-Control-Allow-Origin header.

The API should support CORS request from status page widget.

[Darcy Parker]

I found https://support.atlassian.com/statuspage/docs/what-are-the-different-apis-under-statuspage/#Status-API which says “We don't allow CORS on private pages or trial pages” It then proceeds to suggest creating a proxy. I can get over this hurdle, but why put up such a hurdle for people evaluating your product? It seems a sandboxed iframe is the workaround.

‌