288305 - ftp password entered in url is mistaken for port

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Piet De Somere]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050329 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050329 Firefox/1.0+

ftp site with authorization
url: ftp://user:[e-mail]
directory listing -> links
When I click on a link, I get message 
"Access to the port number has been disabled for security reasons"
When I right-click and open in new tab/window, it works.

Reproducible: Always

Steps to Reproduce:
1.open ftp site with url and password
2.click on link


Actual Results:  
Irrelevant message (imho)

Expected Results:  
There should be no difference between "open" and "open in new window"


I don't suppose it depends on the specific ftp site, but I saw it at
ftp://kristof:[e-mail]

Same results with latest firefox release / nightly firefox build / nightly
mozilla build

Comment 1

[Giles Robertson]

WFM

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050329
Firefox/1.0+

Comment 2

[Steve England [:stevee]]

Wasn't using ftp://username:[e-mail] disallowed because of security
issues? So you can no longer pass username:password in an URI?

Comment 3

[Piet De Somere]

> Wasn't using ftp://username:[e-mail] disallowed because of 
> security issues? So you can no longer pass username:password in an URI?

https://bugzilla.mozilla.org/show_bug.cgi?id=279296

Apparently what was changed is that, when a url containing username and password
is typed, after loading the page the address bar will show the url without
username and password. 

I can understand that passing un/pw in url would be disallowed completely, but
at the moment it seems to be allowed when I enter the url manually or when I
right click on a link, but not when I left click on a link.

Comment 4

[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 5

[Gervase Markham [:gerv]]

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.