Closed
Bug 266079
Opened 20 years ago
Closed 19 years ago
Accessing an FTP server with a complex URL fails due to invalid CWD
Categories
(Core Graveyard :: Networking: FTP, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: a1291762, Assigned: dougt)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 The following url fails because firefox tries to CWD into a nonexistant directory: ftp://lramsay:Qtopia15zgQIzB@snow.trolltech.com.au:4242/home/lramsay/tmp/qpehome/oldpda/Documents/text/plain/test.txt Firefox tries to open /home/lramsay/src/qtopia-1/src/home/lramsay/tmp/qpehome/oldpda/Documents/text/plain/test.txt/ The extra stuff on the beginning is the $PWD of the FTP server process. Pasting the url into Internet Explorer works. Adding an extra / before the path makes firefox work: ftp://lramsay:Qtopia15zgQIzB@snow.trolltech.com.au:4242//home/lramsay/tmp/qpehome/oldpda/Documents/text/plain/test.txt Reproducible: Always Steps to Reproduce: 1. Open FireFox 2. Paste in a complex URL (containing uername, password, port and file that is under several directories) Actual Results: FireFox tries to open a non-existant directory causing the FTP operation to fail. Expected Results: FireFox should have opened the correct directory. This sort of URL is used when talking to a Qtopia/Opie device (eg. Zaurus). If you have access to a Qtopia device you can test against the (limited) FTP server that it uses for file transfers. Since the Qtopia device does not use a "standard" FTP server there's a possibility that the FTP server is sending something to FireFox that is confusing it but I am tempted to discount this since Internet Explorer handled the URL just fine.
Comment 1•20 years ago
|
||
->Networking:FTP
Assignee: firefox → dougt
Component: General → Networking: FTP
Product: Firefox → Core
QA Contact: general → benc
Version: unspecified → 1.7 Branch
Comment 2•19 years ago
|
||
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/
Comment 3•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•6 months ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•