Closed Bug 811337 Opened 13 years ago Closed 13 years ago

Add a hash to the mini manifest

Categories

(Marketplace Graveyard :: API, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2012-11-22

People

(Reporter: clouserw, Assigned: basta)

Details

Our apps have mini-manifests, for example: https://marketplace-dev.allizom.org/app/hawshansperif-bogiki-pencou/manifest.webapp Please add a "hash" field (sha256 is fine) to the manifest which contains a hash of the package. You can add a comment that says sha256 was arbitrary and it is currently an unused field. If someone eventually needs a different hash we can change it, just some hash is needed. We're adding this so the etag changes with each package update. It's possible a package could be uploaded with the same file size right now and an update wouldn't be detected by the platform.
Assignee: mbasta → mattbasta
It's true we currently md5 the mini manifest contents to generate the etag. But we could md5 the contents + package hash without the need to add an unused field to the manifest if we'd rather... https://github.com/mozilla/zamboni/blob/master/mkt/detail/views.py#L86
(In reply to Rob Hudson [:robhudson] from comment #1) > It's true we currently md5 the mini manifest contents to generate the etag. > But we could md5 the contents + package hash without the need to add an > unused field to the manifest if we'd rather... > https://github.com/mozilla/zamboni/blob/master/mkt/detail/views.py#L86 That works too. There is discussion about removing any extra fields from the manifest already, so sure, let's keep it all in the etag for now. Thanks.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.