ftp reget (resume) not functioning correctly

RESOLVED EXPIRED

Status

()

Core
Networking: FTP
--
major
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Todd, Assigned: dougt)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

Hi All,

   I do not have a modem friendly phone line.  Consequently, my modem 
is continually hanging up in the middle of downloads.

   Problem:  (Windows) Mozilla 1.5 and Firebird 0.7 do not get along 
with a lot of ftp site's "reget" (resume) command and you have to 
re-dial and start over, and re-dial and start over, and re-dial and start 
over, yada, yada, yada.   Very, very frustrating!
   
   Mozilla's reget seems to work fine with Mozilla.org's web site, but 
very few others. I have been able to access these download perfectly
using (Linux) gFTP's reget (resume) command: sometimes with as many 
as six re-dials and resumes!

   I would like:

1)  fix the problem with reget (resume)

2)  add a pop up to "overwrite" , "resume" or "cancel" when
saving on top of a file fragment from a previous crashed down load

   Here is an ftp site you can practice on:

        ftp://ftp.bitdefender.com/pub/updates/bitdefender_v7/cumulative.zip

   You can simulate the problem by unplugging your modem part way
through the download.

   As a gift to those of us not blessed with good phone lines, please 
implement this quickly!

Many thanks,
--Tony
aewell@gbis.com

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
.
Assignee: general → dougt
Component: Browser-General → Networking: FTP
QA Contact: general → benc
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 bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.