Closed Bug 1182587 Opened 9 years ago Closed 9 years ago

Set CORS allow-origin header for fetch from cdn

Categories

(Content Services Graveyard :: Tiles: Content Front-End, defect)

Product:
Content Services Graveyard
Component:
Tiles: Content Front-End
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Mardak, Unassigned)

References

Details

(Whiteboard: [story]) 

For bug 1182449, we'll have an iframe hosted at https://tiles.cdn.mozilla.net/iframe.html that will be making XHR requests to https://tiles.services.mozilla.com/v3/links/fetch/en-US/hello

This should just be setting the header:

Access-Control-Allow-Origin: https://tiles.cdn.mozilla.net

It'll also be sending ping requests to https://tiles.services.mozilla.com/v3/links/{view|click} but the response body is empty, so it doesn't really matter that the UA blocks the response.
Both oyiptong and mostlygeek agree that this should be done at the app level instead of modifying nginx config.
Assignee: nobody → oyiptong
We need to set the origin on both the onyx fetch endpoint and on the S3 bucket
mostlygeek suggests we set:

Access-Control-Allow-Origin: *
Depends on: 1182602
Depends on: 1182603
Whiteboard: .? → [story]
Assignee: oyiptong → nobody
Depends on: 1183120
Blocks: 1183347
Depends on: 1183778
All parts are working with CORS per bug 1183778 comment 6
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.