49018 - Proxy: Browser Fail to Connect to Web Servers - "http://" in migrated prefs.

Status: VERIFIED DUPLICATE of bug 30387

(Core :: Networking, defect, P3)

Description

[Charles Loosen]

I did a quick search and did not find this reported.

I recently installed the Netscape PR2 and noticed this bug. I wanted to find 
out if I would experience it in the latest nightly build so I downloaded 
2000081308

Steps to duplicate:
1) download nightly build, unzip, click on mozilla.exe
2) wait the 40 seconds it takes for mozilla to load
3) attempt to visit www.abcnews.com - should get error "www.abcnews.com could 
not be found.  Please check the name and try again."
4) attempt to revise the URL to http://www.abcnews.com/ - should get error " 
www.abcnews.com could not be found. Please check the name and try again."
5) attempt to visit www.netscape.com. - should get error "www.netscape.com 
could not be found. Please check the name and try again."

Anyway, I'm unable to use mozilla or the netscape version to connect to any web 
site.

I'm running:

Acer Apire 2175
Windows 95b 4.00.950
IE5 5.00.3105.0106
Netscape 4.73
64 Megs EDO Ram
200 MHz MMX Processor
4.3 GB HD

I sure hope someone can duplicate this bug. I did not have problems with 
mozilla the last time I checked the nightlies about 1 month ago. Good luck in 
confirming this.

Comment 1

[Jeffrey Baker]

Sounds like you are having DNS problems at your location.  WFM on Linux
2000-08-14-05 and every other build for the last 18 months.

Comment 2

[Asa Dotzler [:asa]]

worksforme on win32 and Mac builds form 08/15

Comment 3

[Charles Loosen]

DNS problems? OK..but that doesn't tell me why Mozilla doesn't work while my 
other browsers, including Netscape 4.73, do. I'd really like someone to test 
this on a fresh install of Win95a or Win95b to confirm this bug. This could be 
a major problem for users on older versions of win32.

Comment 4

[Charles Loosen]

After chatting with jwg in #mozillazine I think I've figured out what was going 
on here. In Netscape 4.73 I had my proxy connection set to http://proxy:8080  
somewhere along the line something got screwed up when Mozilla imported my 
profile from netscape. When I would set mozilla to use my Netscape profile I 
would not be able to access web sites. When I created a new profile with no 
imported proxy settings, everything functioned normally.  

Could there be some sort of problem with Moz importing the proxy settings from 
the 4.x Netscape browser??

Comment 5

[Gervase Markham [:gerv]]

Changing to component Profile Migration.

[e-mail] - could you please tell us a) what your proxy-related 
settings are in NS 4.x and b) what Mozilla translates them into (Preferences | 
Advanced | Proxies). Thanks. :-)

Gerv

Comment 6

[Asa Dotzler [:asa]]

reassign.

Comment 7

[Asa Dotzler [:asa]]

Charles Loosen, can you please follow up with requested information.  THanks.

Comment 8

[Grace Bush]

see also bug 39015 and try a build from this week (9/22 or better)

Comment 9

[dbragg]

Actually this isn't a profile migration bug, it's a bug with the part of the 
program that is supposed to read proxy server preferences (if indeed this 
setting is even stored as a preference). That code is supposed to read the 
old pref and convert it (if necessary) to something useable in the new world.

The Profile Migration code was originally designed to simply make available all 
the old settings in a way that they could be read and modified, NOT to do the 
modification itself.  Exceptions crept in in the area of Mail/News prefs but 
that's because the actual Mail and News files needed to be moved to completely 
new locations in the new archtecture.  This is not the case with simple settings 
like proxy servers.

Asa, Do you know what part of the code deals with reading and using proxy server 
preferences?

Comment 10

[Grace Bush]

Don, this looks like a preferences component bug- reassigning
sairuh- agree?

Comment 11

[sairuh (rarely reading bugmail)]

hm, if this is proxy stuff, my hunch is that this belongs to networking.
however, gagan/tever, if it's really a prefs issue, do send it over to
prefs-backend. thx!

Comment 12

[Gervase Markham [:gerv]]

Confirming, seeing as this has been looked at by several engineers.

Gerv

Comment 13

[Gagan]

yup this is ours... neeti the preference needs to be able to handle http://foo 
instead of just foo in it. (see 4.x prefs for examples) -- let me know if you 
need help with this.

Comment 14

[benc]

mass move, v2.
qa to me.

Comment 15

[benc]

*** This bug has been marked as a duplicate of 30387 ***

Comment 16

[benc]

VERIFIED:
Still unclear if this is talking about manual (dupe of 30387) or if it is really
PAC broken (bug 53080).

Both are fixed, so it doesn't matter, but a good lesson in getting full steps
before you resolve.