217283 - [patch Included] Use http to download Rhino, ftp doesn't work.

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Robert Leland]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030821
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030821

Clicking on ftp://ftp.mozilla.org times out,
Solution use http://ftp.mozilla.org 

nboyd%atg.com was last Author.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Robert Leland]

Attachment: Patches to use http download instaed of ftp

Comment 2

[Asa Dotzler [:asa]]

The ftp links don't time out for me. Is this a firewall or proxy issue or something?

Comment 3

[Robert Leland]

That's possible it, I'll check my Firewall settings

At least there should be an alternate link to use http,
then close the ticket out.

-Rob

Comment 4

[Martin Poirier]

I confirm this, and let me add more. I can't connect to any FTP site, and the
first time I noticed this behaviour was aroung Septembet 15 (although I am not
downloading builds every day these days, 1 or 2 weeks might have passed from the
previous build.)

I'm on Win98SE, using the latest mozilla trunk build. At first, I thought the
mozilla ftp site was down, so I didn't report the bug right away, but then I
noticed  I couldn't connect to any ftp site. I can connect to these sites using
IE and a ftp client though.

There is a discussion about that in the mozillazine forums.
http://forums.mozillazine.org/viewtopic.php?p=217703#217703

I didn't change any mozilla setting lately, and a new profile doesn't fix the
issue either. This isn't a proxy nor firewall issue, as I am not using any of
these at the moment.

When trying to connect to a ftp site, I see "beginning FTP transaction" in the
status bar, and then I see "resolving host ftp.mozilla.org" as an example, and
this "resolving host" message remains there forever (I don't even seem to get a
timeout; I waited 10 minutes).

Comment 5

[Martin Poirier]

WFM now using today's trunk build. My guess is yesterday's checkin in bug
219376, but I may be wrong. Anyways, anyone else can confirm that it works now?

Comment 6

[Daniel Wang]

nboyd%atg.com fixed this