Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

app.update.url set new default value

  • 2 件の返信
  • 2 人がこの問題に困っています
  • 6 回表示
  • 最後の返信者: cor-el

more options

I want change the default value from the update url permanently to my update server, but firefox only accept the default value for the updates. It changed after every update to the old value.

I want change the default value from the update url permanently to my update server, but firefox only accept the default value for the updates. It changed after every update to the old value.

すべての返信 (2)

more options

Your Firefox reported itself to be Firefox 43, so I have to wonder, "what updates?"

If something is holding you back from upgrading to Firefox 55 (or Firefox 52 ESR if you prefer the Extended Support Release), please let us know so we can suggest solutions or workarounds. Version 43 is not secure; Mozilla discloses security flaws after each new release.

Sometimes Firefox reports the wrong version because that information was saved in a preferences file. You can check using the steps in this article: How to reset the default user agent on Firefox.

And see: http://kb.mozillazine.org/Locking_preferences

more options

You can use the mozilla.cfg file in the Firefox program folder to set or lock preferences and run privileged JavaScript code.

The mozilla.cfg file needs to be in the main Firefox program folder.

These functions can be used in the mozilla.cfg file:

defaultPref();	// set new default value
pref();	// set pref, allow changes in current session
lockPref();	// lock pref, disallow changes

This requires a local-settings.js file in the "defaults/pref" folder where the channel-prefs.js file is located that specifies to use mozilla.cfg.

pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);

The mozilla.cfg file and possibly local-settings.js need to start with a comment line (//).

See Configuration:

See also: