Closed Bug 295400 Opened 20 years ago Closed 9 years ago

FTP connection attempt timeout should be configurable

Categories

(Core Graveyard :: Networking: FTP, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: timwi, Unassigned)

Details

(Whiteboard: [wontfix?])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I can't connect to an FTP through Firefox because the server is slow. I keep
getting the message "The operation times out when attempting to contact
<domainname>."

I know the server works because other (more patient) FTP clients can connect to
it without problems.

There appears to be a network.ftp.idleConnectionTimeout setting in about:config,
but it doesn't seem to have an effect on this. I set it to 50 minutes, but the
above error message appears much faster. I assume it only kicks in after the
connection is actually established.

Reproducible: Always

Steps to Reproduce:
->Networking:FTP
Assignee: nobody → dougt
Component: General → Networking: FTP
Product: Firefox → Core
QA Contact: general → benc
Version: unspecified → 1.7 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This is still a problem. I understand it isn't easy to reproduce because you
need a slow FTP server to do so, but it's still a problem...
mass reassigning to nobody.
Assignee: dougt → nobody
The "idle" timeout is for existing connections, not creating connections.

The timeout time is based on your system default. I *think* windows has a line command, if you try the same thing (ftp 127.0.0.2), it should return a similar looking error at about the same delay.

-> NEW, but I don't know if we will ever do anything about this. IMHO, this should be set at the system level.
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to benc from comment #5)
> -> NEW, but I don't know if we will ever do anything about this. IMHO, this
> should be set at the system level.

found no related bugs
Severity: major → normal
Whiteboard: [wontfix?]
only critical ftp fixes now
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.