If an non Mozilla update is being used, and that update fails, we should not offer a mozilla download
Categories
(Firefox :: Enterprise Policies, enhancement, P3)
Tracking
()
People
(Reporter: mkaply, Unassigned)
Details
We're getting reports from folks that have their own update server setup and they aren't serving empty XML when there is no update.
So Firefox sees the broken XML, says the update failed and offers to get Firefox from our website.
If someone is using an alternate update URL, we shouldn't be offering for them to download Firefox from our servers, we should just not show the dialog (or not have a link).
https://github.com/mozilla/policy-templates/issues/496
(and yes, I know they should be serving <updates></updates> but since we don't publish how to build your own update server, people don't know to do this)
Comment 1•6 years ago
|
||
Hmm. I'm a little concerned about this one. The reason we're so pedantic about the XML is as a defense mechanism, and I'm not sure I'm willing to give that up based on a setting that doesn't quite tell us to do that. I'd be happy with a separate policy that provides an explicit signal to disable the manual prompts though, or if that's too much then maybe we can work something out.
| Reporter | ||
Comment 2•6 years ago
|
||
I'd be happy with a separate policy that provides an explicit signal to disable the manual prompts though, or if that's too much then maybe we can work something out.
That's a much better idea. I'll do that. And I'll try to get my update server documentation updated.
| Reporter | ||
Updated•6 years ago
|
Description
•