Yeah, I'll be happy to show my configuration again.
Jehan, instead of using all-redhat.js I created a new file (Firefox is smart enough to read every js file in /usr/lib<64>/firefox-3.0/defaults/preferences/) called vendor.js.
/usr/lib/firefox-3.0/dw-config.cfg:
//point to the autoconfig directory on the web server
lockPref("autoadmin.global_config_url", "http://proxyconfig/autoconfig/");
I found that if the 'lockPref("autoadmin.global_config_url","<your_url>")' line is the first line in the dw-config.cfg file, it gave me errors. That comment line eliminated the error. (?)
dw-config-cfg points to a general directory, rather than a specific file, because I use the same two files for Mozilla, Thunderbird and Firefox: that directory contains an index.cgi that determines the software being used with $ENV{'HTTP_USER_AGENT'} and then points to the appropriate autoconfig file.
Yeah, I'll be happy to show my configuration again. 64>/firefox- 3.0/defaults/ preferences/ ) called vendor.js.
Jehan, instead of using all-redhat.js I created a new file (Firefox is smart enough to read every js file in /usr/lib<
/usr/lib/ firefox- 3.0/defaults/ preferences/ vendor. js: config. obscure_ value", 0); config. filename" , "dw-config.cfg");
pref("general.
pref("general.
/usr/lib/ firefox- 3.0/dw- config. cfg: "autoadmin. global_ config_ url", "http:// proxyconfig/ autoconfig/");
//point to the autoconfig directory on the web server
lockPref(
and finally, the link you described above:
/usr/lib64/ firefox- 3.0/defaults/ autoconfig --> /usr/lib64/ xulrunner- 1.9/defaults/ autoconfig
I found that if the 'lockPref( "autoadmin. global_ config_ url","< your_url> ")' line is the first line in the dw-config.cfg file, it gave me errors. That comment line eliminated the error. (?)
dw-config-cfg points to a general directory, rather than a specific file, because I use the same two files for Mozilla, Thunderbird and Firefox: that directory contains an index.cgi that determines the software being used with $ENV{'HTTP_ USER_AGENT' } and then points to the appropriate autoconfig file.
Hope that helps.