Closed Bug 55238 Opened 19 years ago Closed 19 years ago

ftp://user@host/ with trailing slash handling is incorrect

Categories

(Core :: Networking: FTP, defect, P3)

defect

Tracking

()

VERIFIED INVALID
Future

People

(Reporter: mozilla, Assigned: dougt)

References

()

Details

ftp://user@host/ (with trailing slash) still goes to user's home directory when 
in fact it should log in as the user then go to "/"
Status: NEW → ASSIGNED
Target Milestone: --- → Future
notes for future: the underlying problem is that necko URI's canonicalize (sp?) 
the URIs to have a trailing slash for path if none is present. This makes the 
ftp://user@host and ftp://user@host/ be the same. So FTP has no way to detect 
the difference. 
Note that rfc1738 says that ftp://foobar/ should just be where the server
puts it.

Also note that if Mozilla is using HTTP rules to canonicalize ftp URIs then it's
probably violating rfc2396.
Hi dougt, welcome to necko :)
Assignee: rjc → dougt
Status: ASSIGNED → NEW
Blocks: 62352
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
tenthumbs, what part of rfc2396 would be in violation.  I think, if anything, we
would be (and are) violating rfc1738.  Please feel free to write up bugs where
we break this rfc, (for example we do not handle type).


This bug is invalid since rfc1738 specifies that all url-path of a FTP URL has
the following syntax:

<cwd1>/<cwd2>/.../<cwdN>/<name>;type=<typecode>

where the cwd's could be encoded. 

so, if you wanted to go to the root drive, your url would look like:

ftp://user@host//
-or-
ftp://user@host/%2F

UGLY, but the standard.

Component: Networking → Networking: FTP
QA Contact: tever → benc
Whiteboard: dupeme
VERIFIED: Mozilla 1.0 timeframe, is covered in testcases.
The RFC was effectively worked around in bug 84242.
Status: RESOLVED → VERIFIED
Depends on: 84242
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.