316711 - browser.fixup.alternate.suffix should not be used when URL contains hostname with trailing slash

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Sven Neuhaus]

I went to see if the jobs TLD is operational already (i noticed there are NS records for .jobs) so I tried going to
"http://www.jobs/" in Firefox 1.5beta2.

Firefox obviously sent the request to jobs.com (there are no DNS records for www.jobs)
The URL in the location field did not change, however!

I consider this to be two bugs:
a) I think if the browser.fixup.alternate.suffix is used, the URL in the location field should reflect that (this is a SECURITY problem!)
b) browser.fixup.alternate.suffix should not be used at all when the user enters a URL with a slash after the hostname.

I am not using a proxy server.

Comment 1

[Peter van der Woude [:Peter6]]

(In reply to comment #0)
> The URL in the location field did not change, however!
WFM (the url did change to http://www.jobs.com/) , Linux only ?

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051116 Firefox/1.5 ID:2005111603

Comment 2

[Jesse Ruderman]

WFM Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051108 Firefox/1.5

Comment 3

[Sven Neuhaus]

FYI, I have this problem a) on Debian unstable both using the debian packaged firefox:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Debian package 1.0.7-1)

and the Firefox 1.5 beta 2 tarball:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

but NOT with the latest nightly 2005-11-16-05:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051116 Firefox/1.5

So I guess a) got fixed?


Sounds like you were able to reproduce problem b) ?
Don't you agree that browser.fixup.alternate.suffix should only be in effect when there is entered w/out a trailing slash? Otherwise there is no way to make sure which site you access.

Comment 4

[Sven Neuhaus]

"when there is entered" should be "when the hostname is entered"

Btw, Peter and Jesse, please make sure you entered "http://www.jobs/" in the location bar, not "www.jobs" (doesn't really matter now that a) is fixed, just curious if it was indeed a linux only problem)

Comment 5

[Daniel Rogers]

There is  an additional problem here.

I can not go to any .museum by typing just that in the address bar with "fixup" enabled.  Apparently, firefox doesn't check to see if the address exists before applying fixup.  .museum is a root delegated address, so /anything/.museum is a valid hostname, but you can't get to them by typeing the domain name.  Presumably, fixup should only be applied if the final component is not a valid top level domain, but firefox doesn't have an up-to-date list of tlds.

Comment 6

[Sven Neuhaus]

I can't reproduce the problem in comment #5, however, problem b) is still there in the latest nightly (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060627 Minefield/3.0a1).

Entering http://www.jobs/ (with trailing slash) is "fixed" and I end up at http://www.jobs.com/
Don't you agree that fixup should only be applied when the hostname has no trailing slash?

Comment 7

[Sven Neuhaus]

I still see this problem with Firefox 2.0.0.3, alas now it looks like it tries to resolve "www.jobs" and only after the timeout it then goes to "www.jobs.com". A small improvement.

Comment 8

[Tyler Downer [He/Him]]

This bug is part of a query for Firefox bugs that have Status set to NEW, but have version field set to 2.0 or older and have not changed in over 800 days.

http://tiny.cc/forgottennewbugs

If you still see this bug, or if it is still valid with Firefox 3.6.10 or a firefox 4 nightly build, please update the version field and steps to reproduce.

Comment 9

[:Felipe Gomes (needinfo for replies!)]

I could not reproduce problem b) anymore testing with FF 23 Nightly on OSX 10.8. Please reopen if this is incorrect