Queue: Add CORS support to the taskcluster-artifacts bucket

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: jlal, Assigned: jonasfj)

Tracking

Details

Comment hidden (empty)
(Assignee)

Comment 1

4 years ago
We should probably make the queue do this... When it starts up... instead of having configuration externally...
Assignee: nobody → jopsen
Summary: Add CORS support to the taskcluster-artifacts bucket → Queue: Add CORS support to the taskcluster-artifacts bucket
(Assignee)

Updated

4 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

4 years ago
I've added the following policy... We'll do a putBucketCors everytime the queue starts...

> AllowedOrigins: ['*'],
> AllowedMethods: ['GET', 'PUT', 'HEAD', 'POST', 'DELETE'],
> AllowedHeaders: ['*'],
> MaxAgeSeconds:  60 * 60

Let me know if there is any reason (beside obscurity) not to keep this as permissive as possible.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: TaskCluster → Queue
Product: Testing → Taskcluster
You need to log in before you can comment on or make changes to this bug.