280910 - Firefox does not recognize WinXP DNS Suffix Search List

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[jt2]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Especially nasty in Intranets.
E. g., in the WinXP network preferences, the following DNS Suffix Search List
may be specified: servers.companydummy.corp (then e. g. a "ping
server1.servers.companydummy.corp" may be shortened to "ping server1").
Also, "http://server1.servers.companydummy.corp" normally can be shortened to
"http://server1" (at least in Internet Explorer). This does NOT work in Firefox!

Reproducible: Always

Steps to Reproduce:
see details

Comment 1

[OstGote!]

I guess you mean something like bug 88217. Duplicate? See Bug 161699 too.

What does exactly not work? Can you open http://server1/

Comment 2

[OstGote!]

If you have to use a proxy see Bug 91587 too.

Comment 3

[Nickolay_Ponomarev]

Reporter, please answer question in comment 1, also please review the bugs
linked and tell us whether this report is a duplicate of any of them.

Comment 4

[jt2]

(In reply to comment #1)
> I guess you mean something like bug 88217. Duplicate? See Bug 161699 too.
> 
> What does exactly not work? Can you open http://server1/

I tried to understand the other mentioned bug reports that are "similar".
However, I'm not sure if my bug is a real duplicate - maybe a programmer with
more DNS background can "decide" this.
In Bug 88217, the comment #4 is the short description of my problem: "... the
URL http://foo/ should go to the same host as would be pinged by 'ping foo' at a
command/shell prompt in the OS in question."

Additional Info:
1) Internet Explorer does behave (correctly) this way.
2) I am using a proxy server. However, I do not have any influence on the
configuration of this central Intranet proxy, so the "fix" must be on the
Firefox application side

Thanks
Jens

Comment 5

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

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

Comment 7

[alankanczes]

I had this issue.  When I selected the option "Use System Proxy Settings" the issue was resolved.