Closed
Bug 134901
Opened 23 years ago
Closed 23 years ago
Time left is negative (has "-") and size is 0K for ftp downloads
Categories
(Core Graveyard :: Networking: FTP, defect)
Core Graveyard
Networking: FTP
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: mrasp, Assigned: bbaetz)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
1.14 KB,
patch
|
dougt
:
review+
darin.moz
:
superreview+
jesup
:
approval+
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020401
BuildID: 2002040108
When downloading something the value behind "Time Left" contains one or more "-"
characters.
Reproducible: Always
Steps to Reproduce:
1. Download file
2.
3.
Actual Results: 00:0-45
0-1:0-5
Expected Results: 00:00:45
00:01:05
Comment 1•23 years ago
|
||
Same with 2002040103/Win2K. BTW saving hasn't info about whole size of
downloaded file, it shows status: 8013KB of 0KB (at 50.6KB/sec).
OS: Linux → All
![]() |
||
Comment 2•23 years ago
|
||
This may well be a networking:ftp issue. It seems to be a problem in the
regular download dialog too, not just in download manager.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: PC → All
Summary: Time Left display contains "-" characters → Time left is negative (has "-") and size is 0K for ftp downloads
Comment 3•23 years ago
|
||
I've seen this too today, without using download manager.
to networking:ftp
Assignee: blaker → bbaetz
Component: Download Manager → Networking: FTP
QA Contact: sairuh → benc
Assignee | ||
Comment 4•23 years ago
|
||
Oops. I readded the response code to mResponseMsg, but didn't change the code
which parsed this.
Patch coming up.
Assignee | ||
Comment 5•23 years ago
|
||
Cut the response code out of the message before trying to parse it.
![]() |
||
Comment 6•23 years ago
|
||
*** Bug 135042 has been marked as a duplicate of this bug. ***
Comment 7•23 years ago
|
||
Comment on attachment 77370 [details] [diff] [review]
patch
r=dougt
Attachment #77370 -
Flags: review+
Comment 8•23 years ago
|
||
*** Bug 135147 has been marked as a duplicate of this bug. ***
Comment 9•23 years ago
|
||
Comment on attachment 77370 [details] [diff] [review]
patch
Index: nsFtpConnectionThread.cpp
> if (mResponseCode/100 == 2) {
>- PRInt32 conversionError;
>- PRInt32 length = mResponseMsg.ToInteger(&conversionError);
>- if (NS_FAILED(mChannel->SetContentLength(length))) return FTP_ERROR;
>+ mFileSize = atoi(mResponseMsg.get()+4);
>+ if (NS_FAILED(mChannel->SetContentLength(mFileSize))) return FTP_ERROR;
> }
>
>- if (mResponseCode == 213)
>- mFileSize = atoi(mResponseMsg.get());
so, this bug is about an error w/ the way the file size is parsed, but
previously we were only assigning mFileSize on a 213... now we do it for
any 2xx message. is that ok?
sr=darin
Attachment #77370 -
Flags: superreview+
Comment 10•23 years ago
|
||
Please update this bug with an [adt1] - [adt3] impact rating (or take it off the
list if it doesn't even rate adt3.) Thanks!
Assignee | ||
Comment 11•23 years ago
|
||
We were actually parsing teh file size twice, before, and looking at the first
digit only is correct, since that indicates what sort of response it was.
Comment 12•23 years ago
|
||
Comment on attachment 77370 [details] [diff] [review]
patch
This makes us look bad, very visible.
a=rjesup@wgate.com
Attachment #77370 -
Flags: approval+
Assignee | ||
Comment 13•23 years ago
|
||
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 14•23 years ago
|
||
Comment 15•23 years ago
|
||
*** Bug 136541 has been marked as a duplicate of this bug. ***
Comment 16•23 years ago
|
||
VERIFIED: rc1,w98.
should be covered by file handler tests anyhow.
Status: RESOLVED → VERIFIED
Updated•1 year ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•