Closed
Bug 1158738
Opened 10 years ago
Closed 10 years ago
When auto-signing files are cached by cdn and it results in hash mismatch
Categories
(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect)
addons.mozilla.org Graveyard
Admin/Editor Tools
Tracking
(Not tracked)
RESOLVED
FIXED
2015-05
People
(Reporter: magopian, Assigned: magopian)
References
Details
(Whiteboard: [qa-])
When we auto-signed some add-ons on production, we saw an issue with update requests that would result in "hash mismatch" errors like the following (taken from https://bugzilla.mozilla.org/show_bug.cgi?id=1158467#c6): >1429965505402 addons.xpi WARN Download of https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suite-2.6.9.22-sm+fn+fx.xpi failed: Downloaded file hash (0c6774cd5479a315253eb403c6a7c074658154630ac9c4bc481aa0aba6eb16a8) did not match provided hash (c12fd43da6db7a976518b3df6cbcf99ff6260d18554a87d0c13332b4c5417b6e) >1429965775267 addons.xpi WARN Download of https://addons.cdn.mozilla.net/user-media/addons/1843/firebug-2.0.9-fx.xpi failed: Downloaded file hash (74d5d66bdaa0b78542d791db2e8480f7f396f85345b85524417991b1d597674a) did not match provided hash (dd3da6e3ca2ea15f062cd69d457bc99071c78ae349406f3cb69555aceb65010d) >1429965775279 addons.xpi WARN Download of https://addons.cdn.mozilla.net/user-media/addons/472577/classic_theme_restorer_customize_ui-1.3.0-fx.xpi failed: Downloaded file hash (9aa2446b3f2db9b93aee2e3cc1a6eb947370717f6abe3e8e071d5e04f812e23f) did not match provided hash (6c3f1212daa9b0cac44d1c225f9f906f1040507b6ec89d72df2736bf1cea86a0) We need to change the download url the same way we did for bug 1155813.
Assignee | ||
Comment 1•10 years ago
|
||
PR: https://github.com/mozilla/olympia/pull/527
Assignee | ||
Comment 2•10 years ago
|
||
Fixed in https://github.com/mozilla/olympia/commit/892825c21141e6f6c1f584c06a46ad6bedc5dc24
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Updated•9 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
•