ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

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

  • 8 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 2 ნახვა
  • ბოლოს გამოეხმაურა HellerIT

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)

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)

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?

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?

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

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:

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.

შერჩეული გადაწყვეტა

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.

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