We have two different profiles for FF 1.5 running dial-up on an XP Pro
machine with SP2 installed. Our Norton Internet Security is set to
allow all connections for FF.
Our problem is that only one of the profiles will set our localhost
proxy properly. Both profiles should be using the same proxy setting of
"localhost:8080 with and exception for 127.0.0.1". Since we don't open
both profiles at the same time, there should not be any conflict. The
second profile can be set to the Manual setting and it will function for
that session; but when FF is closed either and the end of the connection
or for any reason; the next time FF is opened, the proxy connection will
have reset itself to Auto Detect. In the Auto Detect mode our
accelerator software does not function at all.
Is there some prefs setting that should be set in both of the profiles
to insure that the localhost proxy is set properly. Maybe a setting in
the pref.js? BTW we have the localhost proxy set in the MS Internet
options also.
Any suggestions?
Thanks,
--
Howard H. Heflin
NOSPAM_...@netscape.net
The usual removals are required to reply.
Is the problem consistent with the same profile? Or is it just a matter
of one (no matter which one) not behaving?
--
Chris Ilias - Mozilla Champion
mozilla.test.multimedia moderator
Mozilla links <http://ilias.ca>
(Please do not email me tech support questions)
Hi Chris,
The problem seems to be consistent with one profile not holding the set.
If your suggestion is to create a new profile; how can we insure that
all of the saved passwords, cookies, and bookmarks are moved to the new
profile. I can handle the bookmark part; but am not sure about the
other items.
I have created separate <prefs.js? files located in the individual paths.
The misbehaving path is C:\Documents and Settings\J\Application
Data\Mozilla\Firefox\Profiles\xxxxxxx.J This <prefs.js> file contains
the following proxy lines:
user_pref("network.proxy.http", "Localhost");
user_pref("network.proxy.http_port", 8080);
user_pref("network.proxy.no_proxies_on", "127.0.0.1");
user_pref("network.proxy.type", 4);
The <prefs.js> file in path that works contains the following proxy lines:
user_pref("network.proxy.http", "Localhost");
user_pref("network.proxy.http_port", 8080);
user_pref("network.proxy.no_proxies_on", "127.0.0.1");
user_pref("network.proxy.type", 1);
There is a rudimentary (no date) prefs.js file in the C:\Program
Files\Mozilla Firefox\defaults\ folder.
The only difference I see is the 'network.proxy.type' line where the
misbehaving line is set to "4" and the one that works is set to "1".
Admittedly, I have not tried changing that one line; because I don't
really know what it does and I've been reluctant to muck around with
these files without understanding the overall potential consequences.
Suggestions?
--
Howard H. Heflin
NOSPAM_...@netscape.net
The usual removals are required to reply.
Stop SPAM !!!!
Chris and Kim,
Thanks for the assistance.
Interestingly enough the issue turned out to be in the <user.js> file
not the <prefs.js> file. I had been changing the <prefs.js> file while
the <user.js> file contained the "network.proxy.type=4" which was
overruling the <prefs.js> "network.proxy.type=1". After making the
correction in the <user.js> file, all is well with the world.
The nice part about this exercise was that I didn't have to create a new
profile and go through that whole "whoha".
Thanks again. :-)