Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

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

In Firefox 67.0 a .jnlp-file does not provide the "open" option when downloaded

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

more options

In Firefox version 66.0.4 when I download a .jnlp-file it provides the option to either save the file or open it in Java Web Start. Now that I updated to Firefox version 67.0 I can only save the file. The option to directly open the file using Java Web Start is not available anymore.

In Firefox version 66.0.4 when I download a .jnlp-file it provides the option to either save the file or open it in Java Web Start. Now that I updated to Firefox version 67.0 I can only save the file. The option to directly open the file using Java Web Start is not available anymore.

選ばれた解決策

There have been security changes in Firefox 67 regarding how to handle executable files. This was discussed in a restricted bug (1392955), we can only see the outcome.

この回答をすべて読む 👍 1

すべての返信 (8)

more options

Firefox gives a warning when you open an "executable" file from that downloads list.

Previously, there was a preference called browser.download.manager.alertOnEXEOpen you could set to false to avoid the message. That preference was removed.

But don't panic, there is a new one. Here's how you set it up:

(0) Select and copy the new preference name:

browser.download.skipConfirmLaunchExecutable

(1) In a new tab, type about:config in the address bar and press Enter/Return. Click the button accepting the risk -- this change involves some risk.

(2) In the search box above the list, type or paste EXE and pause while the list is filtered

(3) Right-click a blank space and click New, then Boolean.

  • In the little dialog that comes up, paste the preference name and click OK.
  • Click true and then click OK. (If you do not get the options of true and false, you might not have selected Boolean, so cancel and start again.)

Now when you launch a .jnlp or other executable from the Downloads list, it should go straight to the system without the intervening confirmation dialog. Not the safest thing if you tend to download questionable files, but more convenient.

(4) To switch this off, to protect against accidentally running other kinds of executables, double-click the browser.download.skipConfirmLaunchExecutable preference to switch the value from true to false (then in the future, when this is needed, double-click to switch it to true)

more options

Sorry, I answered a different JNLP-related question than the one you asked!

Since JNLP is considered an executable file, there's no "Open" option for it, no. Did that just change in Firefox 67?

more options

There should be an Open choice available for JNLP (Java Network Launched Application; application/x-java-jnlp-file) when Java is installed properly (I still have it on Linux).

Maybe check the handlers.json file in the profile folder (see about:profiles -> root). Do the .jnlp file start JavaWS when you download and save the file?

more options

You can also check the Network Monitor what MIME that the server ends for this .jnlp file.

more options

cor-el said

There should be an Open choice available for JNLP (Java Network Launched Application; application/x-java-jnlp-file) when Java is installed properly (I still have it on Linux).

Yup, it is a Windows thing:

more options

jscher2000 said

Thank you guys for your help. Really appreciate it.

Do I understand this correctly: when an extension is in the executable extensions list Firefox will not display a "open with" option, right?

In this case there has to be an issue in Firefox v.66 because I can prove that a .jnlp file can be "opened with Java Web Start" on FF v.66. I have a testsystem with version 66.0.4 installed where I can demonstrate this. As soon as I update Firefox to version 67 the option disappears.

more options

選ばれた解決策

There have been security changes in Firefox 67 regarding how to handle executable files. This was discussed in a restricted bug (1392955), we can only see the outcome.

more options

Thank you. This is exactly what I needed to know.