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

Avatar for Username

Mozilla サポートの検索

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

詳しく学ぶ

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

How can we force firefox to check its trusted certificate store on every request?

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 55 回表示
  • 最後の返信者: thready

thready
thready

We have an application on localhost that gets installed from our page. We happen to be running over HTTPS. We wrote code in our installed application to add the certificate to firefox's trusted store. The page that provides the installer for this app then autodetects that it's installed by making HTTPS requests to it. Only, it doesn't work in Firefox since Firefox needs to be restarted so that it reads its trusted store.

Is there any way for us to make firefox read its store again and not rely on a cached result?

Thanks! Mike

We have an application on localhost that gets installed from our page. We happen to be running over HTTPS. We wrote code in our installed application to add the certificate to firefox's trusted store. The page that provides the installer for this app then autodetects that it's installed by making HTTPS requests to it. Only, it doesn't work in Firefox since Firefox needs to be restarted so that it reads its trusted store. Is there any way for us to make firefox read its store again and not rely on a cached result? Thanks! Mike

すべての返信 (2)

guigs
guigs

Hi, I asked on the #security channel about this and they said the work around for this is to add the certificate through the Firefox Certificate Menu in the Preferences/Options menu under Security.

However they are also interested in what makes it difficult for you to use a certificate from a CA that Firefox trusts by default? As this is something we are looking to improve on. I have asked them to follow this thread for your feedback.

Thank you and we are looking forward to your post!

この投稿は guigs により に変更されました

thready
thready 質問者

Thanks for your response. We dropped this approach and went with a plugin instead. Basically we just need to communicate to localhost for the "richer thick client experience", but ran into the issue of mixing https as origin with http to localhost being blocked by the browser (personally I think mixing should be ok for localhost calls but I'm not a security expert).

Kind regards, Mike