From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1+) Gecko/20010622 BuildID: 2001062204 I have seen this happen twice. The download size is 0k and so the time remaining is also hosed. This seems to only be a problem with exe files? Reproducible: Always Steps to Reproduce: 1.go to:http://www.eudora.com/cgi-bin/export.cgi?productid=EUDORA_win_51 2.dialog pops up with total size as 0. 3.Also, time remaining is hosed Actual Results: 0k total size and time remaining is a mess. Expected Results: Correct total download size and time remaining.

Confirmed build 2001062204 win32 on win98

argg... I can't seem to reproduce this bug anymore with the same build above. I was able to do so yesterday.

umm I'm not sure what I did but I can reproduce it again...

reasigning

I'm not seeing this on Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010627 Netscape6/6.1

I've seen this today with 2001062904 on Windows 2000 SP2. It doesn't seem to occur as often as before, but it still occurs...

There's not a time when I don't see this happening lately. ZIP file saved to disk exhibits this behavior in 2001062904.

WFM with build 2001063008 on Win2k (SP2) using the URL listed for this bug. Jake

Tested same URL, same build Win98. Bug still occurs.

prob a dup.

Downloads never show time remaining when using proxy: Bug 89113 Downloads with unknown size are displayed incorrectly: Bug 84410 *** This bug has been marked as a duplicate of 84410 ***

In build 2001070108 win32, I can only reproduce when keep-alive is off.

Reopening: with this bug I can only reproduce when keep-alive is off, with the other bug it doesn't matter if keep-alive is on or off. This might be caused by the fact that the testcase in the other bug purposely don't send filesize info. The question is in this bug why does keep-alive makes a difference?

_basic: No, I know this is still a dup of bug 84410. Please pay closer attention before reopening dups. *** This bug has been marked as a duplicate of 84410 ***

Skewer: I can understand that it is actually a duplicate of bug 84410, note that however that bug is going to be fixed in UI context not networking context, there are two problems here. I was going to investigate this bug further as a networking problem (as it is in networking http). I'm going to leave this as a dup as I see that you have created bug 89113 for the networking (proxy) problem (which this is also a dup of).