Closed Bug 84625 Opened 24 years ago Closed 24 years ago

FTP Get results in error

Categories

(Core Graveyard :: Networking: FTP, defect)

x86
Other
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.4

People

(Reporter: dneri98, Assigned: dougt)

Details

Build 2001-06-06-20, Win98 (and much older builds) Build 2001-06-01-04, Win2K sp1 I can't post the FTP address directly because it's password protected and business related. However, I can still describe the issue: Behavior: On saving a .ZIP file from a second level directory (i.e. root/sub/somezip.zip), I get the following ALERT box: "/root/sub/somezip.zip: The directory name is invalid." I checked the Mozilla-generated HTML code, and it looks intact. Expected: Successful FTP transaction. I can successfully get this file from Netscape 4.7x. ...Filing another FTP related bug right after this, as I'm not sure they're connected.
reporter: do you still see this in a more recent build?
Yes, I still see this in 2001-06-18-04. I just downloaded the absolute newest, and it's still the same exact build. Is that because of the pending 0.9.2 release? In either case, I still see it. :( Oh, and marking 4xp since I am successful in Netscape. <Shrug>
Keywords: 4xp
Hmm, I think the reason the newest build was the same is ANOTHER FTP bug, but we won't get into that. Nonetheless, after getting the newest (2001-06-21-04) I still see it. Here's something that may be of big help. I put the username and password into the URL to access the directory, i.e. ftp://user:pass@server.com/subdir/ Methinks this may be what's causing all the links (except parent dir) to fail. <Shrug>...
Still confirming on build 2001-06-26-11. To reproduce the problem, I would suggest logging into an FTP server with the username and password embedded in the URL. Changing severity to major (even though I would opt for more) because it's blocking my work on the job. I have to download at least one file off the server each night.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
What is the status of this bug? I haven't heard anything from DougT, even when he took control of the bug...he was silent! (That bastard...)
You'd probably hear a better response if you treated people with a little more respect.
<QA Ignore> Gagan, I truly take offense to that. I even re-read my comments to be sure... The last comment I had was full of sarcasm and winking, hence the "that bastard" comment. My other comments have been suggestions and observations. I can't find a hint of disrespect. Nonetheless, if I have offended anyone, I apologize. I just don't like seeing bugs stagnant for over a month, that's all. If Doug had said something when he changed status to ASSIGNED I would be resting easy. </QA> Anyway, I don't know how they have the server set up in my (protected) example, but is it safe to assume it has something to do with the embedded password?
Dwayne, Making this bug invalid as I have no clear way to reproduce this problem. Can you find a site that exhibits this problem and reopen? I have no problems login into internal ftp servers with a complete ftp uri which includes user/password prehost info.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Doug, I will provide you with my URL via email under the agreement that all information is used solely for testing purposes. Reopening in the meantime. I can still reproduce this with build 2001-07-23-03.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
fine. I really don't care what you got on that site... I am only conserned with address any possible problems. We have less than 20 hours before we miss the 0.9.3 boat. ;-/
bulk move to 0.9.4
Target Milestone: mozilla0.9.3 → mozilla0.9.4
This appears to be fixed.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
QA Contact: tever → benc
Verifying. Thanks guys.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.