[provisioner] Access-Control-Allow-Origin: * is not set on heroku but is locally

RESOLVED INVALID

Status

RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: jhford, Unassigned)

Tracking

Details

Not sure why, but when running in production, the API for the provisioner does not allow cross origin requests.  When I run the server locally, the headers required for this are set correctly.

This blocks the UI for the provisioner.
I'm not sure what is playing tricks on you but CORS headers are present... Maybe it's something else that makes CORS requests fail...

Anyways we certainly validated headers are present.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Resolution: FIXED → INVALID
Component: TaskCluster → AWS-Provisioner
Product: Testing → Taskcluster
You need to log in before you can comment on or make changes to this bug.