1353780 - Some error pages do not return Access-Control-Allow-Origin

Status: NEW

(Data Platform and Tools :: General, defect, P3)

Description

[Chris H-C :chutten]

From mozilla/telemetry-dashboard#243:

"When aggregates.telemetry.mozilla.org returns an error response (as in mozilla/telemetry-dashboard#242), it does not send the Access-Control-Allow-Origin header. This causes errors to appear to be CORS failures, when in fact they are HTTP errors. The server should emit the ACAO header so that the proper error messages appear in the developer console."

This was filed as mozilla/python_mozaggregator#18 but somehow missed the train that would've had it refiled here in BMO.

Comment 2

[Thomas Huelbert]

what the priority on this Chris?

Comment 3

[Chris H-C :chutten]

The sooner we get to it, the nicer it'll be for consumers of aggregates.tmo. tmo itself may need an additional change to react well to the error messages it'll suddenly be able to understand, before user value can be felt.

On a scale from 1 to 5, I'd put it as 3 - sometime this quarter would be nice.

Comment 6

[:shell escalante]

Is this still a need chutten? would you prirorize this work in the next year? if not we'll close and refile as needed.

Comment 7

[Chris H-C :chutten]

This is indeed still needed until TMO Dashboards are decommissioned in favour of GLAM (which is awaiting GLAM's opening up to not need a moz LDAP login). It is a rare thing, so lemme just drop its severity to S4 here.

I would love for Data SRE or whoever has the keys to this service to have the bandwidth to get to this work in the next year (seems like a good task for a new hire, hm?). I can't do it myself, unfortunately.