Closed
Bug 146076
Opened 23 years ago
Closed 22 years ago
URL: problems with relative URLs above ftp home directory
Categories
(Core Graveyard :: Networking: FTP, defect)
Core Graveyard
Networking: FTP
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: moz, Assigned: andreas.otte)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2)
Gecko/20020510
BuildID: 2002051006
I made a bookmark to FTP site of my network which below;
ftp://admin:password@192.168.0.10
Using with Netscape4.7X or 6.X, when I access through this bookmark, I am
located to root(/) directory. But, using MOZILLA, I am located to admin
direcory and MOZILLA dose not show "Up to higher level directory". So, I cannot
move my location to other directory involving root directory.
I am very inconvenienced. Please fix this BUG.
Reproducible: Always
Steps to Reproduce:
I made a bookmark to FTP site of my network which below;
ftp://admin:password@192.168.0.10
Using with Netscape4.7X or 6.X, when I access through this bookmark, I am
located to root(/) directory. But, using MOZILLA, I am located to admin
direcory and MOZILLA dose not show "Up to higher level directory". So, I cannot
move my location to other directory involving root directory.
I am very inconvenienced. Please fix this BUG.
Actual Results: MOZILLA dose not show "Up to higher level directory".
Expected Results: I can access to other directory which allowed to user "admin".
Otherwize using ftp://admin:password@192.168.0.10/../../../,
I can access to root directory, but when I click to "home", "etc", "var" etc.
which allowed to access to user "admin", Alert window is opend which say "550 No
such file or directory".
Finaly, I cannot access to other directory.
have you turned on the debug/networking pref for directory listing format to
display as XUL tree?
Comment 2•23 years ago
|
||
-> FTP
Assignee: sgehani → bbaetz
Component: XP Apps → Networking: FTP
QA Contact: paw → benc
Comment 3•23 years ago
|
||
This is not a bug - logging in will place you in your home directory. To access
the root directory, use:
ftp://user@host// (ie two slashes)
I think theres a separate bug on showing/not showing the "go up a directory" in
that case. Andreas, do you have a number for that?
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 4•23 years ago
|
||
No, not at the moment, but I will look. We should add that the current behavior
follows the standards, NS4.x and NS6.x do not.
most requests for "up" are for XUL, but if we hop into a home directory, we can
go implicitly up, but I don't think it is obvious until you try the same URL w/
a "//" at the end...
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 6•23 years ago
|
||
I have no time to work on mozilla at the moment, so dougt is taking over FTP
open ftp bugs -> him
Assignee: bbaetz → dougt
Status: UNCONFIRMED → NEW
Comment 7•23 years ago
|
||
what bradley said.
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
REOPEN:
Mozilla 1.1, allplats.
You can play with hacking the URL when you are put into your home directory, but
the links in the HTML get broken:
ftp://user@server/ (puts you into /Users/user)
You can go up by adding ".." or "../" to the URL bar.
However, the links in the HTML at that level are incorrct.
A folder /Users/file would appear in the display of
ftp://user@server/../ (puts you into /Users/)
with a link of:
ftp://user@server/file (which points to /Users/user/file).
The link should say:
ftp://user@server/../file (which points to /Users/user/../file -> /Users/file)
The base is in the HTML is correct, so we must do some thing that removes the
trailing ".." when we glue the HREF of the file to the BASE.
Status: RESOLVED → UNCONFIRMED
OS: Windows 2000 → All
Hardware: PC → All
Resolution: FIXED → ---
| Assignee | ||
Comment 9•23 years ago
|
||
Yes, this is a known bug. I once tried to fix it but tinderbox HTML is broken
and does not work after the patch applied. Unless tinderbox is fixed this can't
be fixed. See bug 120396 for details.
Comment 10•23 years ago
|
||
-> NEW
Tried to clarify problem in summary.
Status: UNCONFIRMED → NEW
Depends on: 120396
Ever confirmed: true
Summary: FTP's bug: cannot access to allowed directory → URL: problems with relative URLs above ftp home directory
Comment 11•23 years ago
|
||
Andreas, is this a dup?
| Assignee | ||
Comment 12•23 years ago
|
||
Making this bug dependend on bug 122133 which itself is blocked by 120396,
instead of making it dependend on 120396. A fix for bug 122133 (which is the
more general case) will fix this too. I'm not sure I would call this a dup, at
least this bug can be better found than the more technical stuff about CoalesceDir.
This is not a FTP only problem, it should be fixed for al relative URLs, but as
long as tinderbox generates wrong urls, a fix for this will certainly immediatly
backed out, as it happend with bug 119071 which created 122133 as spinoff.
Feel free to assign this bug to me if it can wait for tinderbox to be fixed.
| Assignee | ||
Comment 14•22 years ago
|
||
bug 122133 which this bug depends on (or is a dupe of) now contains a fix. But
this fix still breaks tinderbox because tinderbox generates bsd urls. No hope
until tinderbox gets fixed.
| Assignee | ||
Comment 15•22 years ago
|
||
The .. behaviour is now fixed with the checkin for bug 207298, the reason this
bug was reopened ... closing again
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → FIXED
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
•