User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 All links on the top of this page linking back to a http://ftp.mozilla.org return 404 errors. This page i was fed by bugzilla as the place to get the latest builds. the downloads themselves seem to be working OK. I am spcificaly refering to the links right at the top of this page Reproducible: Always Steps to Reproduce: 1.load referance url 2. click on a link back to http://ftp.mozilla.org at the top of the page 3. Actual Results: 404 error returned from the server Expected Results: appropriate page
OK, i went page to this page again and it was compleatly different. After doing a nslookup on ftp.mozilla.org and finding multiple servers i started feeding in ip addresses and found the problem server has ip 220.127.116.11 aka ftp.uni-erlangen.de. All the other servers seem ok, and perhaps this mirror server needs some attention
This German server is one of the secondary official mirrors, see http://www.mozilla.org/mirrors.html. So you have used http://ftp.eu.mozilla.org/. Note: "when you connect to ftp.mozilla.org, you are connecting to one of the United States mirrors". Probably only a temporary problem?
All i did to get sent to this mirror is hit the link on bugzilla that sends you off to get the latest vertions. my ISP seems to have fed me the german mirror's IP from the ns information. i just clicked on the british flag at the top and the error apered.
Oh I see it now. It is the fault of the German mirror, they have not set up the English pages, so you will get the 404 error if you click the British flag. It has nothing to do with mozilla.org. I will inform the German server admin. Please resolve this bug as INVALID (has nothing to do with Mozilla/mozilla.org). Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → INVALID
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.