12
edits
(Update Scenarios) |
m (typo fix.) |
||
Line 21: | Line 21: | ||
1. Suppose install.rdf contains an em:updateURL of http://foo.com/update.rdf. When FF retrieves the resource at http://foo.com/update.rdf, if the resource does not contain an em:updateHash element or the value of the em:updateHash element is incorrect, the update is not installed. | 1. Suppose install.rdf contains an em:updateURL of http://foo.com/update.rdf. When FF retrieves the resource at http://foo.com/update.rdf, if the resource does not contain an em:updateHash element or the value of the em:updateHash element is incorrect, the update is not installed. | ||
2. Suppose install.rdf contains an em:updateURL of https://foo.com/update.rdf. When FF retrieves the resource at https://foo.com/update.rdf, FF will install the update even if no em: | 2. Suppose install.rdf contains an em:updateURL of https://foo.com/update.rdf. When FF retrieves the resource at https://foo.com/update.rdf, FF will install the update even if no em:updateHash element exists (assuming there are no problems with the certificate for foo.com). If, however, em:updateHash does exist, it is checked for validity against the update. | ||
3. Suppose install.rdf contains no updateURL. FF EM exclusively contacts AMO via https:// for updates. | 3. Suppose install.rdf contains no updateURL. FF EM exclusively contacts AMO via https:// for updates. | ||
--[[User:Grimholtz|Grimholtz]] 12:18, 9 July 2007 (PDT) | --[[User:Grimholtz|Grimholtz]] 12:18, 9 July 2007 (PDT) |
edits