Closed
Bug 220221
Opened 21 years ago
Closed 21 years ago
Attempt to access this FTP site frequently times out; if Mozilla reaches the site the display is incomplete.
Categories
(Core Graveyard :: Networking: FTP, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 178210
mozilla1.6alpha
People
(Reporter: jjw, Assigned: darin.moz)
References
()
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4) Gecko/20030624
When I attempt to access this IBM FTP site, Mozilla's behavior varies. About
20-30% of the time the operation times out. When this happens, upon dismissing
the timeout message, an empty FTP directory appears. Even when the operation
does not time out the directory list is sometimes empty even though there are
actually files in the directory. When the directory comes up empty, usually
clicking on up to higher directory displays the parent (fromibm) directory, but
sometimes this also results in an empty display. When the parent directory
displays, clicking on os2 usually displays the os2 directory. Once the
directory has been displayed, the files in it can be downloaded without problems.
When Netscape 4.6.1 is used to access this site, the "header" section of the
directory listing contains a couple of reminders to read the README files.
These messages are not displayed when Mozilla is used to access the site. While
the failure to display these messages is only a minor problem in and of itself,
it appears that it is the presence of these messages that cause Moailla to get
into difficulties. iptrace reveals that the messages are being received but are
not being correctly recognized and displayed.
Reproducible: Always
Steps to Reproduce:
1. Enter the URL: ftp://testcase.boulder.ibm.com/ps/fromibm/os2/
2.
3.
Actual Results:
Sometimes times out, sometimes displays empty directory, sometimes displays
complete file list but no "header" information.
Expected Results:
This was copied from Netscape 4.6.1 using the clipboard. The lines with an
asterix in position 1 are the ones that are not present in the Mozilla display.
Current directory is /ps/fromibm/os2
*Please read the file README
* it was last modified on Wed Oct 31 08:42:25 2001 - 693 days ago
*Please read the file README_PS.TXT
* it was last modified on Tue Aug 5 08:15:11 2003 - 50 days ago
Up to higher level directory
24696tf2.zip 18 Kb Mon Sep 22
10:32:00 2003 Zip Compressed Data
44527fix.zip 7854 Kb Sun Sep 21
23:11:00 2003 Zip Compressed Data
awtvj.zip 644 Kb Mon Sep 22
03:51:00 2003 Zip Compressed Data
hpfsdbg.zip 28093 Kb Mon Sep 22
06:59:00 2003 Zip Compressed Data
ipsrsym.ZIP 23850 Kb Wed Sep 24
06:52:00 2003 Zip Compressed Data
mhpfs386.zip 59287 Kb Mon Sep 22
08:41:00 2003 Zip Compressed Data
Comment 1•21 years ago
|
||
Confirming new. I see this too in 20030924 PC/WinXP. OS->All
Best I could get was an empty directory and a dialog box with the error "425
Can't open data connection"
Was able to get right in using Opera 7.2.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: other → All
Comment 2•21 years ago
|
||
I too noticed this bug (see my note
http://forums.mozillazine.org/viewtopic.php?t=25838 for more info) some time
after the 20030911 win32 build.
Fortunately, FTP connections seem to be working fine again in the 20031007 win32
build! (However, FTP was not working as recently as the 20031004 win32 build,
the last available win32 build before 20031007.)
Comment 3•21 years ago
|
||
Is this materially distinguishable from bug 178210? I think most if not all IBM
ftp servers are set up the same.
Does the bug 210125 fix need to go on the 1.4.x branch? Maybe these two are
obsolete since that fix?
Assignee | ||
Comment 4•21 years ago
|
||
-> me for investigation
Assignee: dougt → darin
Severity: normal → major
Target Milestone: --- → mozilla1.6alpha
Comment 5•21 years ago
|
||
*** This bug has been marked as a duplicate of 178210 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•10 months ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•