Closed Bug 147119 Opened 18 years ago Closed 13 years ago

Domain guessing: mozilla adds www. and .com when accessing server on lan

Categories

(Core :: DOM: Navigation, defect)

x86
All
defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: calvinwalton, Assigned: adamlock)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523
BuildID:    2002052309

On our lan, we have a computer named "hotblack". When trying to access it as
"http://hotblack/~username/" , mozilla tries to add "www." and ".com" to
"hotblack", resulting in the page being unresolved. This does not happen with
just "http://hotblack/"

We have a dns server running - if hotblack's ip address is used, it still tries
to access www.hotblack.com

Reproducible: Always
Steps to Reproduce:
1. Have computer on lan run webserver - users directories as format /~user
2. try to access user directory, using ip address or computer name


Actual Results:  tries to access http://www.computername.com/~user

Expected Results:  accesses http://computername/~user or http://ipaddress/~user
If we use the domain that hotblack is in (galaxy), then mozilla only tries to
add a "www."
I.E. "http://hotblack.galaxy/~user" -> "http://www.hotblack.galaxy/~user"
-> docshell.

reporter: please be prepared to provide more information, like a sample document.

Some aspects of this should have been disabled.
Summary: mozilla adds www. and .com when accessing server on lan → Domain guessing: mozilla adds www. and .com when accessing server on lan
Is this still happening? The domain guessing behavior should not be affected by
the "path" stuff in the URL.
Component: Networking → Embedding: Docshell
*** Bug 170287 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 95390 ***
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Another example of neededing to get a clear description from the reporter.
Probably my fault...

Looking at the inital report carefuly, suggests that if you typed:

http://1.2.3.4/ (the correct IP address for an unavailable server, you would get
domain guessing via a reverse lookup)

http://www.unavailable.com/

Very scary. If the reporter is still reading this, your clarification would
still be appreciated.
QA Contact: benc → adamlock
REOPEN: 

This has nothing to do w/ bug 95390, this is likely a domain guessing bug.

I think, that for a while, there was a behavior that took any unqualified
hostname (hostname w/o ".") and premptively did "www.hostname.com".

Many reports seem to suggest that a lookup for "www.hostname.com" is happening
even when "hostname" exists in the local domain. 

With a properly configured computer, a resolver would try "hostname.localdomain"
before erroring.

As for the the IP address -> www.hostname.com behavior, the only explaination I
have is that a server could return a redirect to "http://hotblack", which would
trigger domain guessing.
Status: RESOLVED → UNCONFIRMED
QA Contact: adamlock → benc
Resolution: DUPLICATE → ---
Assignee: new-network-bugs → adamlock
QA Contact: benc → adamlock
-> defaults
QA Contact: adamlock → benc
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/
Firefox 1.07 guesses windows xp lan name correctly.
EG: Entering the macine name only (hydra) into the address bar gave me the
default web page of my dev box (http://hydra/).


(In reply to comment #9)
> 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/
> 
Closing this as INVALID, works correctly for me on latest release and on trunk, if it's still happening to anyone on a recent build, please feel free to comment and this bug will be reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago13 years ago
Resolution: --- → INVALID
should have been -> WORKSFORME
Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.