Closed
Bug 1182587
Opened 10 years ago
Closed 10 years ago
Set CORS allow-origin header for fetch from cdn
Categories
(Content Services Graveyard :: Tiles: Content Front-End, defect)
Content Services Graveyard
Tiles: Content Front-End
Tracking
(Not tracked)
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.
Reporter | ||
Comment 1•10 years ago
|
||
Both oyiptong and mostlygeek agree that this should be done at the app level instead of modifying nginx config.
Updated•10 years ago
|
Assignee: nobody → oyiptong
Comment 2•10 years ago
|
||
We need to set the origin on both the onyx fetch endpoint and on the S3 bucket
Comment 3•10 years ago
|
||
mostlygeek suggests we set:
Access-Control-Allow-Origin: *
Updated•10 years ago
|
Whiteboard: .? → [story]
Updated•10 years ago
|
Assignee: oyiptong → nobody
Reporter | ||
Comment 4•10 years ago
|
||
All parts are working with CORS per bug 1183778 comment 6
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•