Closed
Bug 1221748
Opened 10 years ago
Closed 10 years ago
API URL to signed add-on file is a 404
Categories
(addons.mozilla.org Graveyard :: API, defect, P1)
addons.mozilla.org Graveyard
API
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kumar, Assigned: kumar)
References
Details
When using `jpm sign` on stage to sign an add-on, it appeared to run successfully but the add-on file URL was a 404. Example:
$ curl -I 'https://addons.allizom.org/firefox/downloads/file/318224/github_tab_width-0.0.60-fx.xpi?src=api'
HTTP/1.1 404 NOT FOUND
...
|
Assignee | |
Updated•10 years ago
|
Priority: -- → P1
|
|
Assignee | |
Comment 1•10 years ago
|
||
ah, it's because you have to be logged in to download the file. Perhaps we need an API endpoint.
|
|
Assignee | |
Comment 3•10 years ago
|
||
The status check response now returns an authenticated API URL to download the file (bug 1221759).
Implemented in:
https://github.com/mozilla/olympia/pull/880
https://github.com/mozilla-jetpack/jpm/pull/377
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•