Search Support

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.

Learn More

Clarification about JNLP files

  • 7
  • 1 nwere nsogbu anwere nsogbu a
  • 15 views
  • Nzaghachi ikpeazụ nke datboxistrash

more options

Hello all,

I've read some bug reports and discussions about the JNLP files blocked in Firefox ( JNLP should be treated as executable , Should not treat JNLP files as Executables (revert bug 1392955) on ESR-68 , Improve usability for JNLP and other executables and JNLP should not be considered an executable extension ). All I'm understanding is it has been blocked since Firefox 67, then "allowed" back again, then blocked for security purposes in Firefox 78. To sum it up, the bug 1576762 is still open, JNLP are still blocked. Nowadays, it's not possible to directly launch a JNLP file, you've got to download it and run it thereafter. Am I right ?

Also, I've taken note of the Firefox ESR release "too late". I've installed the "mainstream" Firefox release on a server in order to be remotely used by end users (via a RDS server, only to browse a internal website, they can't browse the web). What are the results/differences/cons (except the extended support) ?

Thanks in advance for your replies. Jo.

Hello all, I've read some bug reports and discussions about the JNLP files blocked in Firefox ( [https://bugzilla.mozilla.org/show_bug.cgi?id=1392955 JNLP should be treated as executable] , [https://bugzilla.mozilla.org/show_bug.cgi?id=1576616 Should not treat JNLP files as Executables (revert bug 1392955) on ESR-68] , [https://bugzilla.mozilla.org/show_bug.cgi?id=1576762 Improve usability for JNLP and other executables] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1648786 JNLP should not be considered an executable extension] ). All I'm understanding is it has been blocked since Firefox 67, then "allowed" back again, then blocked for security purposes in Firefox 78. To sum it up, the bug 1576762 is still open, JNLP are still blocked. Nowadays, it's not possible to directly launch a JNLP file, you've got to download it and run it thereafter. Am I right ? Also, I've taken note of the Firefox ESR release "too late". I've installed the "mainstream" Firefox release on a server in order to be remotely used by end users (via a RDS server, only to browse a internal website, they can't browse the web). What are the results/differences/cons (except the extended support) ? Thanks in advance for your replies. Jo.

All Replies (7)

more options

There is a pref available that you need to create as a new Boolean pref on the about:config page.

  • browser.download.skipConfirmLaunchExecutable

You can open the about:config page via the location/address bar. You can click the button to "Accept the Risk and Continue".


more options

Hi cor-el,

Actually, I've seen what you suggest on my previous question. Currently, the only solution is "Save file" (or cancel...). I'd like to have the choice between "Open" and "Save" or if it's not possible, I'd like to directly run/launch the jnlp file right after the download.

I've tried with the "Applications" section in Firefox settings but it doesn't work.

Thanks for you help. Jo

more options

Does anyone have any idea please ?

Jo

more options

Did you create a new Boolean pref browser.download.skipConfirmLaunchExecutable = true like I posted above, as that would suppress the prompt ?

more options

Hello cor-el,

I did. Actually, I've followed what was said in my previous question. I also followed these two tutorials : - how to configure firefox to autorun jnlp files (java web start) - Windows 10 - Firefox with Java Web Start

But none of them worked. The Applications settings in Firefox's options wasn't saved. I chose the program to open the JNLP files (Java Web Launcher), closed my browser and opened it back again and the setting was set to "Always ask".

I've installed the last Firefox ESR version this weekend and the behaviour isn't the same (as the "standard" Firefox). I got back the "Open with" choice. But now, the JNLP extension doesn't appears in the Firefox Applications settings. It's closer to what's expected from my end-users. I'm gonna be eager but I guess there's no way to have a "one-click" solution (just a click on the button and the JNLP is downloaded, opened and launched --> that would be perfect for them) ? Thanks in advance.

Jo

more options

Hi Jo, is your second screenshot --

-- what you get now after creating the browser.download.skipConfirmLaunchExecutable boolean preference set to true? Or was that from a different Firefox?

I think you should consider switching the managed installation to the Extended Support Release of Firefox 78 since you won't have to contend with monthly feature changes that could create extra support issues. See: Choose a Firefox update channel.

(fixed the missing second closing bracket- c)

Edeziri site na cor-el

more options

Hello jscher,

Actually, I never got that screen with the managed installation. With or without the boolean preference. This screen has appeared from the moment I installed Firefox 78.4.0 ESR (I uninstalled Firefox 81 managed installation). I'll stick to that release channel. Thanks.

Jo