736405 - Firefox does not respect 'browser.fixup.alternate.enabled'

Status: RESOLVED DUPLICATE of bug 469157

(Firefox :: Address Bar, defect)

Description

[Andrew]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

Followed the steps listed here to deactivate Domain Guessing:

http://support.mozilla.org/en-US/kb/Location%20bar%20search#Domain_Guessing


Actual results:

Restarted Firefox but Domain Guessing still active -- Firefox adding www and com to internal hostnames like 'abc' i.e. rewriting them to 'www.abc.com'.  Additionally I changes the 'browser.fixup.alternate.prefix' and '.suffix' values to empty strings, restarted Firefox, but it was still adding www. and .com to internal hostnames.


Expected results:

Domain Guessing should not be happening. Any internal hostnames should be left untouched.

Comment 1

[Tim (fmdeveloper)]

What happens if you open a command prompt and type "ping abc" and then "nslookup abc"?

Comment 2

[Andrew]

The issue presented on a proxied work PC. I tested just now on my home PC and the .fixup.alternate setting and .keyword settings behave as expected when deactivated.

So the issue seems limited to a specific configuration.  On the same work PC I have used both Chrome and IE (going through same corporate proxy) without them failing to handle internal hostnames (no prefix, no TLD) the way Firefox did on that PC, so something is definitely up. It will require more testing on that specific PC now that I've confirmed it's not a general bug.

I won't be at the affected PC til next week.  Once I know more I'll post my observations/results here.  Thanks.

Comment 3

[Andrew]

Ok, back at my work pc now, where the problem exhibits. Just checked and the problem is still there, Firefox insists on prefixing www. and suffixing .com despite the settings below:

browser.fixup.alternate.enabled;false
browser.fixup.alternate.prefix;www.
browser.fixup.alternate.suffix;.com
browser.fixup.hide_user_pass;true
browser.fixup.use-utf8;false

keyword.URL;
keyword.enabled;false

Using an example internal hostname of 'corpapps'...

PING:

C:\Users\[redacted]>ping webapps

Pinging [redacted].[redacted].[redacted].[redacted].au [172.20.XX.XX] with 32 bytes of data:
Reply from 172.20.XX.XX: bytes=32 time<1ms TTL=127
Reply from 172.20.XX.XX: bytes=32 time<1ms TTL=127
Reply from 172.20.XX.XX: bytes=32 time<1ms TTL=127
Reply from 172.20.XX.XX: bytes=32 time<1ms TTL=127

Ping statistics for 172.20.XX.XX:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


NSLOOKUP:

C:\Users\[redacted]>nslookup webapps
Server:  [redacted].internal.dom
Address:  172.20.XX.XX

Name:    [redacted].[redacted].[redacted].[redacted].au
Address:  172.20.XX.XX
Aliases:  [redacted].internal.dom

Comment 4

[Andrew]

Clarifying:

>> Using an example internal hostname of 'corpapps'...

The actual example internal hostname used in my test was 'webapps', not 'corpapps', which is why it says:

>> C:\Users\[redacted]>nslookup webapps

I missed that in my redacting/munging rendering that instance moot.

Comment 5

[Andrew]

If it helps, here's a tracert to the internal domain name that firefox is mishandling:

C:\Users\[redacted]>tracert webapps

Tracing route to perweb23.[redacted].[redacted].[redacted].[redacted] [172.20.51.23]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.20.207.1
  2    <1 ms    <1 ms    <1 ms  perweb23.[redacted].dom [172.20.51.23]

Trace complete.

Comment 6

[Victor]

I'm experiencing the same problem on 19.0 beta on Mac OS 10.8.2

I have some local domains on the hosts file (e.g., mylocalsite.dev) and it pings and resolves correctly.

I have set:
browser.fixup.alternate.enabled;false
(the rest of the .fixup settings remain as default)

This is what happens:

If I start typing "mylocal" the url bar suggests "mylocalsite.dev/" (the rest of the text, "site.dev/" being marked in blue to denote the suggestion), at this point I can hit enter and Firefox will add www. and the connection fails.

However, if I press the "right" key to go to the end of the line, delete the "/" and then hit enter, it correctly navigates to mylocalsite.dev without adding the www.

Hope this helps and I'm happy to provide more details if needed.

Comment 7

[Steve]

Same problem here,entering 'test.mysite.com.au' takes me to 'www.test.mysite.com.au', regardless of fixup.

My fixup configs are the same as posted by Andrew.

Comment 8

[marcstober]

I'm having this issue, too.

Comment 9

[[:Aleksej]]

= bug 469157?

Comment 10

[Allan Laal]

This is also present in Firefox 25.0 on Ubuntu 12.04 LTS

Comment 11

[David Favor]

This is also present in Version 28 latest beta.

A stupid + ugly bug which should be fixed.

Impossible to test bare domain vs. www content splitting.

Comment 12

[TimWarren]

I am running 33.1 and also observe this behavior for our intranet site: http://intranet/news.html.

Mozilla coverts to http://www.intranet.com/news.html and tries to find this through our proxy.
I tried adding http://intranet/news.html to the "No proxy for" list, but that had no effect.

However adding "intranet" (without quotes) to the "No proxy for" list was successful.
It may also work for other single name intranet sites.

Comment 14

[Binary_101]

I can confirm this bug with FF 35.0.1 in both Normal Mode and Safe Mode. Same behavior as @Wouter Koersen described.