179558 - URL: slash in ftp user name misinterpreted as address

Status: RESOLVED INVALID

(Core Graveyard :: Networking: FTP, defect)

Description

[Todd]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Hi All,

    I am using w2k-p, sp3 and Mozilla 1.1.0.2002082611
(sorry about my upgrading -- I need the spell checker.  :-(  )

    I am using an ftp site that requires a particular user name and 
address -- anonymous is blocked.

    Using the convention in the URL of

             ftp://username:[e-mail]

does not work, as my user name has a slash ("/") in it.   (I did 
not pick my user name.)   Using unicode %2f  in place of 
the slash does not work either.

    Would you please modify the URL line interpreter to wait until sees
the "@" before switches from the username and password to the
address?

Many thanks,
--Tony
[e-mail]


Reproducible: Always

Steps to Reproduce:
1.*
2.*
3.*

Comment 1

[Olivier Cahagne]

-

Comment 2

[benc]

According to the RFC, user should not include a "/", but an escaped character
would be valid:

      userinfo      = *( unreserved | escaped |
                         ";" | ":" | "&" | "=" | "+" | "$" | "," )

Comment 3

[Todd]

Hi Benc,

   When you say "user" are you referring to the user name in the login?
And, which RFC are you referring to?

--Tony

Comment 4

[Andreas Otte]

He is refering to RFC2396 for example which makes it clear that usernames in
urls can not contain a /. However masking it as %2F should work. Maybe in the
ftp protocol we do not unescape the slash before sending the password.

Comment 5

[benc]

I'll try to set up a testcase next week and update this bug.

It would be nice if we had a way of manually authenticating username and
password, right now, we only put up password auth when a user is provided, but
no password. Fixing bug 124561 would have made this easier to analyze.

Comment 6

[Gervase Markham [:gerv]]

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 7

[Todd]

> this bug has had no comments for a long time

Still needs fixen'!  :-)

Comment 8

[Wayne Mery (:wsmwk)]

invalid per comment 4