Closed
Bug 1262218
Opened 9 years ago
Closed 9 years ago
Update domains for permissions
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
Tracking | Status | |
---|---|---|
firefox48 | --- | fixed |
People
(Reporter: andy+bugzilla, Assigned: aswan)
References
Details
Attachments
(1 file)
In bug 1262009 ops want to run the discovery pane on a new domain. That means an update to the permissions for UITour bug 1256598 and AddonsManager bug 1245571.
Comment 1•9 years ago
|
||
The ops bug mentioned in the initial description is a typo it should be bug 1262209
Assignee | ||
Comment 2•9 years ago
|
||
For production UITour and mozAddonManager are both currently exposed to addons.mozilla.org and services.addons.mozilla.org. Should discovery.addons.mozilla.org replace one or both of these or just be added to the list?
For dev, UITour gets permitted domains from a preference setting so there's nothing to do for this issue.
But mozAddonManager uses a hard-coded list which is currently:
addons.allizom.org
services.addons.allizom.org
addons-dev.allizom.org
services.addons-dev.allizom.org
example.com
Bug 1262209 mentions discovery.addons-dev.allizom.org and discovery.addons.allizom.org for dev and staging respectively. Same question: should these replace (part of) the current list or just be added to it?
Flags: needinfo?(amckay)
Reporter | ||
Comment 3•9 years ago
|
||
(In reply to Andrew Swan [:aswan] from comment #2)
> For production UITour and mozAddonManager are both currently exposed to
> addons.mozilla.org and services.addons.mozilla.org. Should
> discovery.addons.mozilla.org replace one or both of these or just be added
> to the list?
>
> For dev, UITour gets permitted domains from a preference setting so there's
> nothing to do for this issue.
> But mozAddonManager uses a hard-coded list which is currently:
> addons.allizom.org
> services.addons.allizom.org
> addons-dev.allizom.org
> services.addons-dev.allizom.org
> example.com
>
> Bug 1262209 mentions discovery.addons-dev.allizom.org and
> discovery.addons.allizom.org for dev and staging respectively. Same
> question: should these replace (part of) the current list or just be added
> to it?
discovery.* can replace services.* in all the above examples.
Flags: needinfo?(amckay)
Assignee | ||
Comment 4•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/46885/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/46885/
Assignee | ||
Updated•9 years ago
|
Attachment #8741979 -
Flags: review?(rhelmer)
Comment 5•9 years ago
|
||
Comment on attachment 8741979 [details]
MozReview Request: Bug 1262218 Update permissions for APIs used for addon discovery
https://reviewboard.mozilla.org/r/46885/#review43899
It might be nice to have constants for these domains instead of having the exact domain names duplicated, but this is not a new issue introduced by this patch so up to you.
Attachment #8741979 -
Flags: review?(rhelmer) → review+
Assignee | ||
Comment 6•9 years ago
|
||
https://reviewboard.mozilla.org/r/46885/#review43899
Yeah, I agree that would be nice but I'm pretty sure the permissions file is just copied verbatim into the build directory so substituting for a centrally defined symbol would entail introducing a pre-processing step. I think I'll leave that for another day :-)
Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Keywords: checkin-needed
Comment 8•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox48:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Assignee | ||
Updated•9 years ago
|
Iteration: --- → 48.3 - Apr 25
You need to log in
before you can comment on or make changes to this bug.
Description
•