Closed Bug 1226703 Opened 10 years ago Closed 10 years ago

CORS issues with http://analysis-output.telemetry.mozilla.org

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: benjamin, Assigned: whd)

Details

I'm having continued CORS issues with http://analysis-output.telemetry.mozilla.org In particular, if I first load a page directly in the browser, and then try to load it cross-origin from a dashboard, the response from cloudfront doesn't include the CORS headers. I've search enough to see that cloudfront+S3+CORS is a finicky setup (in particular you have to have a Varies: Host setting so that each cross-origin load is cached is cached separately). This appears intermittent because the cache expires after an hour, but during prototyping this ends up being a rather big PITA.
:bsmedberg are you still seeing this? There were some cloudfront configuration issues that I believe were sorted out (possibly right after you filed this bug) which included making sure the appropriate headers were whitelisted and setting the default TTL to 1s so that the objects would effectively not be cached.
Flags: needinfo?(benjamin)
We think this is fixed, reopen if we're wrong.
Assignee: nobody → whd
Status: NEW → RESOLVED
Closed: 10 years ago
Priority: -- → P1
Resolution: --- → FIXED
I'll keep an eye out and reopen if necessary.
Flags: needinfo?(benjamin)
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.