464308 - provide downloadable list of mozilla mirrors

Status: REOPENED

(Webtools :: Bouncer, enhancement)

Description

[Przemyslaw Bialik]

On http://www.mozilla.org/mirrors.html
there is no link to download list of mirrors in the txt file.
Such list could be used in squid or other proxy servers / firewalls.

The problem is that Firefox and Thunderbird in some companies are set to
automatically download updates but not all employees have full access to the
internet and so they have problems downloading updates - It would be good for them to have up2date software even if their internet access is limited.

If the idea would be approved I can prepare such list (I have one but it got little outdated) and post the patch so others with similar needs could quickly accomplish what they are looking for.

Comment 1

[Chris More [:cmore]]

Closing old Mozilla.org website bugs due to them not being relevant to the new Python-based Bedrock system. Re-open if this is a critical bug and should be resolved on the new system too.

Comment 2

[Samuel Sidler (:ss)]

Chris More: Thank you for taking the time to actually look at bugs before you close them instead of mass-closing. Oh, wait...

This is still a relevant bug.

Comment 3

[Samuel Sidler (:ss)]

CCing Chris More to this bug, which he closed prematurely.

Comment 4

[Chris More [:cmore]]

Is this still relevant Firefox's silent updates and ESR? What about the Thunderbird news from last week?

The bouncer system knows about all the mirrors and if it could serve up a list, it could be given to this page. This will also need to be converted over to Bedrock in the future.

Comment 5

[Samuel Sidler (:ss)]

(In reply to Chris More [:cmore] from comment #4)
> Is this still relevant Firefox's silent updates and ESR? What about the
> Thunderbird news from last week?

Completely unrelated.

Comment 6

[Dave Miller [:justdave]]

I think there's APIs in the current bouncer to retrieve such a list from it.  I'm not positive though.  I remember it being discussed 4 or 5 years ago because of Microsoft firewall products needing to know for whitelisting purposes.  I don't recall what happened with that though.  A quick search finds me bug 457200 which appears to have never been acted on, but I could swear there was more converstation about it somewhere.  There must be another bug out there...