1014200 - Update Addon hotfix server component

Status: RESOLVED WONTFIX

(Firefox :: General, defect)

Description

[Benjamin Smedberg]

The addon hotfix will need to ask a Mozilla server what build it should update users to. Requirements:

* The client will provide the current version, update channel, buildid, locale, architecture, osversion, and service pack level.
* If the client is up-to-date, the server should reply with a null response.
* If the client is not up-to-date, the server should reply with a link to a Firefox installer and a hash of the installer for verification.
* Server logging of requests is required

For now the requests will be Windows-only.

This should be dirt-simple and shouldn't need a database. We could almost use bouncer, except I don't think it supports crypto-hashes.

* verify that the version is <28 and isn't the most recent ESR24
* then provide the proper link/hash to the current installer

bhearsum am I right that bouncer can't do these things?

Comment 1

[[e-mail] (:bhearsum)]

(In reply to Benjamin Smedberg  [:bsmedberg] from comment #0)
> The addon hotfix will need to ask a Mozilla server what build it should
> update users to. Requirements:
> 
> * The client will provide the current version, update channel, buildid,
> locale, architecture, osversion, and service pack level.
> * If the client is up-to-date, the server should reply with a null response.
> * If the client is not up-to-date, the server should reply with a link to a
> Firefox installer and a hash of the installer for verification.
> * Server logging of requests is required
> 
> For now the requests will be Windows-only.
> 
> This should be dirt-simple and shouldn't need a database. We could almost
> use bouncer, except I don't think it supports crypto-hashes.
> 
> * verify that the version is <28 and isn't the most recent ESR24
> * then provide the proper link/hash to the current installer
> 
> bhearsum am I right that bouncer can't do these things?

Bouncer can't return anything other than a 302 AFAIK. It also only supports a limited amount of incoming data. You could encode most of what you need in "product", but that's not a great solution...

Comment 2

[Gregory Szorc [:gps]]

It was decided in a meeting between Benjamin and I that this feature isn't worth the complexity and that it shouldn't be implemented. The major thought process leading to this decision was that the presumed worst case is that the hotfix updates Firefox to an already out-of-date version and the client has to apply yet another update. However, background updates should handle this and the user won't know it is occurring. The user impact is thus marginal and doesn't justify added complexity and potential for failure.