Filetype handlers policy (jnlp-files)

[André Sänger]

Hello,

some of the web-applications we use are using .jnlp files for specific
functionalitites. These files have to be started with openwebstart or
java web start from oracle. I noticed a regression in the non-ESR
firefox release 99 (99.0+build2-0ubuntu0.20.04.2), in that users no
longer get the option to "launch" the jnlp, instead it is just
downloaded, and - even worse - there is no option to change this
behaviour in firefox-settings by the user (jnlp is no longer listed as a
configurable filetype in settings). I found the corresponding
policies.json setting which allows to restore the old behaviour for
.jnlp files (or application/x-java-jnlp-file mimeTypes).

Luckily firefox-ESR (which most of our users use) does not yet show this
behaviour, jnlp still functions as usual with the latest 91.9.0 release.

Now I am wondering -  is this going to stay this way for the ESR, or is
this a planned change that's going to affect ESR as well? Will at least
the configurability through polices stay?


Also on this topic - some of our applications only work with
openwebstart, others only work with web start from oracle, which is
licensed only for these specific applications. Currently it is up to the
user to select the correct javaws for the specific java-application. Is
it somehow possible to preconfigure this via policies.json? So that a
.jnlp-file from URL/Domain A is started by application a, and a .jnlp
file from URL/Domain B is started by application b?


Thanks

André

[Robert Marcano]

I can´t help you on the internals of how to setup an application handler
for the JNLP on Firefox, I am pretty sure someone will help you about
that, but on the case of running the different implementations, maybe
you can install on these client machines a little program that you set
as the unique handler for the mime type, and that program inspect the
contents of the JNLP XML file, and check maybe the codebase and href
attributes on the file and decide based on that which JNLP client
implementation to call with the JNLP file as argument.

Note: Hopefully your applications vendors are thinking in moving of JNLP
as it is deprecated.

>
>
> Thanks
>
> André
>

[Florent Lagoda]

Hi,

Have same behavior here. See the reports here https://bugzilla.mozilla.org/show_bug.cgi?id=1754525

I am interested with your policies settings to restore the old behavior

Le 03/05/2022 à 18:28, enter...@mozilla.org a écrit :

Filetype handlers policy (jnlp-files)

"André Sänger" <andre....@landkreis-coburg.de>: May 03 04:14PM +0200

Hello,   some of the web-applications we use are using .jnlp files for specific functionalitites. These files have to be started with openwebstart or java web start from oracle. I noticed a regression in the non-ESR firefox release 99 (99.0+build2-0ubuntu0.20.04.2), in that users no longer get the option to "launch" the jnlp, instead it is just downloaded, and - even worse - there is no option to change this behaviour in firefox-settings by the user (jnlp is no longer listed as a configurable filetype in settings). I found the corresponding policies.json setting which allows to restore the old behaviour for .jnlp files (or application/x-java-jnlp-file mimeTypes).   Luckily firefox-ESR (which most of our users use) does not yet show this behaviour, jnlp still functions as usual with the latest 91.9.0 release.   Now I am wondering -  is this going to stay this way for the ESR, or is this a planned change that's going to affect ESR as well? Will at least the configurability through polices stay?     Also on this topic - some of our applications only work with openwebstart, others only work with web start from oracle, which is licensed only for these specific applications. Currently it is up to the user to select the correct javaws for the specific java-application. Is it somehow possible to preconfigure this via policies.json? So that a .jnlp-file from URL/Domain A is started by application a, and a .jnlp file from URL/Domain B is started by application b?

Thanks   André

-- 
Florent LAGODA - Université Rennes 2
Direction du Système d'Information (DSI) - Pôle Proximité
☎ 13.68
--

[Mike Kaply]

We have not allowed JNLP to be opened directly on rapid release for a while now because it's considered an executable. We do allow it on ESR.

I'm working on policy changes to allow this on rapid release. It should make the 102 ESR.

The Firefox 99 changes were something different.

Mike

--
You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/d17a6db8-da91-7a58-e546-2b61a4cef34f%40univ-rennes2.fr.

[Pieter Breugelmans]

Hi Mike, can you advise what we can expect to see for behavior with the upcoming Firefox ESR 102.x? Specifically for JNLP, have you implemented the same alternative handling as what got included in Firefox ESR 91.x for us? As we explained earlier by us (Oracle), the handling of JNLP file type is critical to many of our customers and Firefox should allow for an automated launch / execution of such downloaded files.  JNLP files are merely XML files that are executed by Java on the client.

Note to self:

Bug 1755368  Version 97.0 don't open JNLP files
Bug 1576762  Improve usability for JNLP and other executables

[Mike Kaply]

On Thu, Jun 23, 2022 at 10:23 AM Pieter Breugelmans <pieter.br...@gmail.com> wrote:

Hi Mike, can you advise what we can expect to see for behavior with the upcoming Firefox ESR 102.x? Specifically for JNLP, have you implemented the same alternative handling as what got included in Firefox ESR 91.x for us? As we explained earlier by us (Oracle), the handling of JNLP file type is critical to many of our customers and Firefox should allow for an automated launch / execution of such downloaded files.  JNLP files are merely XML files that are executed by Java on the client.

We have implemented the same policy that Chrome has so that you can specify that JNLP files should be launched via policy.

Bug 1722050 - Implement ExemptDomainFileTypePairsFromFileTypeDownloadWarnings

I'm hoping that's good enough. We can revisit if necessary as we come near the official deprecation date for the Firefox 91 ESR.

Mike

[Pieter Breugelmans]

Thanks a lot for clarifying and pointing out the bug for the same. I'll test this policy next week with the first release of Firefox ESR 102.x to confirm that it is working as per our requirements, and will reply back here with my feedback.

[Osdoba, Sascha]

Hi Mike,

 

we also use JNLP files for some Java web stuff and I tried it with firefox v102 but it seems I don’t get it done.

 

Have you created a new gpo setting? If yes I cant find it. Where is it located and whats the name?

May I am blind but I checked the links and I cant find the name in it.

 

I used policy templates v3.10 and also searched all settings but also with no luck.

 

Thanks Sascha

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/8e48eb5f-1c19-4c32-a431-76cdd483c08cn%40mozilla.org.

[Mike Kaply]

Sorry, I'm behind on getting the GPO updated for this release. I'll be releasing the new GPO updates today or tomorrow.

Mike

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/6a06059dffa840b790f35a65dc2f95aa%40gsi.de.

[Kasper, Ryan V. [US-US]]

Thanks Mike for all your work as always,

 

All - was going through the commit history since last summer to get 102esr ready for early evaluation here – here are some other things I have found between 91-102 (I use policies.json in the distribution folder):

{

  "policies": {

    "UserMessaging": {

      "MoreFromMozilla": false

    },
    "FirefoxHome": {

      "SponsoredTopSites": false,
      "SponsoredPocket": false

   }

  }

}

Other items of note:
Clear bookmarks set with policy/admx/plist - https://github.com/mozilla/policy-templates/commit/b23a559ea939ec91355895fe8afa748cf5005d5e

Cookies “behavior” settings - https://github.com/mozilla/policy-templates/commit/b06395a01a8b538676599667c571d4c3778c95ef

TLS 0rtt - https://github.com/mozilla/policy-templates/commit/9b8b2ff822082c6b3bbf20b8dfc2282bf201eb40

Disable extension updates per-extension - https://github.com/mozilla/policy-templates/commit/d9f05619f3d0dd060de5779ac619e53797282c7d

Google Workspace allow list - https://github.com/mozilla/policy-templates/commit/9e1451245460486f7f5f2945144a6b071bcdf4db

Allow 3^rd party extensions such as uBlock origin to configure policy – example - https://github.com/mozilla/policy-templates/commit/f0b1c73cf24dcc3ed1949dc1d9d84d3c1b30486f

Cipher suites - https://github.com/mozilla/policy-templates/commit/67b5d12193200ca100d976baad9d81a299bfd6e2

SameSite cookies handling - https://github.com/mozilla/policy-templates/commit/986f6e00e8d1fe32a73f996071f94ca4fc6a5c5f

Legacy SameSite cookies - https://github.com/mozilla/policy-templates/commit/733158f519a9a02ff0c17cda5a4d833e172b0ba3

Password Manager exceptions - https://github.com/mozilla/policy-templates/commit/417f958cbfb569456953c7ba642e24bde4570276

 

Anything else anyone has noticed they may want to set or restrict between the ESRs so far?

 

Thank you,

Ryan V. Kasper

Leidos SWD

Ryan.v...@leidos.com

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/CAHueOzDQWcLtjNJEuCJMCDxrBPnTYQe9N0SeUDfgaJuy3of%3DpA%40mail.gmail.com.

[Pieter Breugelmans]

I don"t seem to be able to get the new policy to be recognized by Firefox ESR 102.0. My policies.json looks like:

{
  "policies": {
    "DisableAppUpdate": true,
    "ExemptDomainFileTypePairsFromFileTypeDownloadWarnings": {
        "file_extension": "jnlp", "domains": ["mycompany.example.com"]
        }
  }
}

The about:policies shows that the DisableAppUpdate one is active, but for the other one it shows the following error:

Invalid parameters specified for ExemptDomainFileTypePairsFromFileTypeDownloadWarnings.

Did I misunderstood how to make use of this new policy?

[Kasper, Ryan V. [US-US]]

Hi Pieter - Here is the bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=1722050

and the code:
https://hg.mozilla.org/mozilla-central/rev/43d2e2a15bad

 

Your syntax looks OK to my eyes, but I might be missing something. Mike should have the policies with examples posted soon here with the latest Firefox 102 changes https://github.com/mozilla/policy-templates/commit/417f958cbfb569456953c7ba642e24bde4570276

 

Thank you,

Ryan V. Kasper

Leidos SWD

 

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/966ce154-5e9e-4f08-b434-4c3fa129ee78n%40mozilla.org.

[Mike Kaply]

IT's an array of objects. So it needs to be:

    "ExemptDomainFileTypePairsFromFileTypeDownloadWarnings": [{
        "file_extension": "jnlp", "domains": ["mycompany.example.com"]

        }]

Docs coming soon!

Mike

[Pieter Breugelmans]

So yes, the ExemptDomainFileTypePairsFromFileTypeDownloadWarnings works as intended, meaning the warning message does not show up.

Perhaps a bit of side topic to this thread yet related in terms of file type. Further testing with Firefox ESR 102.0 does raise the question how we can actually configure Firefox in such manner that these .jnlp files can launch automatically. With the changes to the file download flow. ref. https://support.mozilla.org/en-US/kb/change-firefox-behavior-when-open-file and in combination with the new browser policy, I never get to see the JNLP file / mime type being added under Applications. Further more, I never get to see a dialog window that allows me to specify to Always open such files automatically the next time around. Under no circumstances do I get to see the "What should Firefox do with this file?" prompt with Firefox ESR 102.0.

https://docs.oracle.com/javase/tutorial/deployment/webstart/examplesIndex.html

[Osdoba, Sascha]

Hi Mike,

the path to the new “ExemptDomainFileTypePairsFromFileTypeDownloadWarnings“ policy is not correct on the page
https://github.com/mozilla/policy-templates/blob/master/README.md#exemptdomainfiletypepairsfromfiletypedownloadwarnings

instead of “Software\Policies\Mozilla\Firefox\Handlers” it is “Software\Policies\Mozilla\Firefox”

Maybe its possible to copy the scheme of Google, check the screenshot if there is any doubt about it :)

https://chromeenterprise.google/policies/#ExemptDomainFileTypePairsFromFileTypeDownloadWarnings

where you see “directly into the eyes” where the setting is located and whats the name

even with the documentation on the firefox github page I always have to search a lot more at the group policy editor which policy is now the one I want to edit and in which folder is it



Regards,

Sascha






Von: enter...@mozilla.org <enter...@mozilla.org> Im Auftrag von Mike Kaply
Gesendet: Donnerstag, 30. Juni 2022 22:46
An: Pieter Breugelmans <pieter.br...@gmail.com>
Cc: enter...@mozilla.org; Kasper, Ryan V. [US-US] <Ryan.V...@leidos.com>
Betreff: Re: [Mozilla Enterprise] Filetype handlers policy (jnlp-files)

IT's an array of objects. So it needs to be:

    "ExemptDomainFileTypePairsFromFileTypeDownloadWarnings": [{

        "file_extension": "jnlp", "domains": ["http://mycompany.example.com"]
        }]

Docs coming soon!

Mike

On Thu, Jun 30, 2022 at 1:20 AM Pieter Breugelmans <mailto:pieter.br...@gmail.com> wrote:
I don"t seem to be able to get the new policy to be recognized by Firefox ESR 102.0. My policies.json looks like:

{
  "policies": {
    "DisableAppUpdate": true,
    "ExemptDomainFileTypePairsFromFileTypeDownloadWarnings": {

        "file_extension": "jnlp", "domains": ["http://mycompany.example.com"]

mailto:Ryan.v...@leidos.com

 
From: mailto:enter...@mozilla.org <mailto:enter...@mozilla.org> On Behalf Of Mike Kaply
Sent: Wednesday, June 29, 2022 11:31 AM
To: Osdoba, Sascha <mailto:S.Os...@gsi.de>
Cc: mailto:enter...@mozilla.org
Subject: EXTERNAL: Re: [Mozilla Enterprise] Filetype handlers policy (jnlp-files)
 
Sorry, I'm behind on getting the GPO updated for this release. I'll be releasing the new GPO updates today or tomorrow.
 
Mike
 

On Tue, Jun 28, 2022 at 10:19 PM Osdoba, Sascha <mailto:S.Os...@gsi.de> wrote:
Hi Mike,
 
we also use JNLP files for some Java web stuff and I tried it with firefox v102 but it seems I don’t get it done.
 
Have you created a new gpo setting? If yes I cant find it. Where is it located and whats the name?
May I am blind but I checked the links and I cant find the name in it.
 
I used policy templates v3.10 and also searched all settings but also with no luck.
 
Thanks Sascha
 
 
Von: mailto:enter...@mozilla.org <mailto:enter...@mozilla.org> Im Auftrag von Pieter Breugelmans
Gesendet: Donnerstag, 23. Juni 2022 16:36
An: mailto:enter...@mozilla.org
Cc: mailto:mka...@mozilla.com <mailto:mka...@mozilla.com>; mailto:enter...@mozilla.org; Florent Lagoda <mailto:florent...@univ-rennes2.fr>; Pieter Breugelmans <mailto:pieter.br...@gmail.com>
Betreff: Re: [Mozilla Enterprise] Filetype handlers policy (jnlp-files)
 
Thanks a lot for clarifying and pointing out the bug for the same. I'll test this policy next week with the first release of Firefox ESR 102.x to confirm that it is working as per our requirements, and will reply back here with my feedback.

On Thursday, June 23, 2022 at 4:31:32 PM UTC+2 mailto:mka...@mozilla.com wrote:

On Thu, Jun 23, 2022 at 10:23 AM Pieter Breugelmans <mailto:pieter.br...@gmail.com> wrote:
Hi Mike, can you advise what we can expect to see for behavior with the upcoming Firefox ESR 102.x? Specifically for JNLP, have you implemented the same alternative handling as what got included in Firefox ESR 91.x for us? As we explained earlier by us (Oracle), the handling of JNLP file type is critical to many of our customers and Firefox should allow for an automated launch / execution of such downloaded files.  JNLP files are merely XML files that are executed by Java on the client.
 
We have implemented the same policy that Chrome has so that you can specify that JNLP files should be launched via policy.
 

https://urldefense.us/v3/__https:/bugzilla.mozilla.org/show_bug.cgi?id=1722050__;!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOOiRxcJU$

 
I'm hoping that's good enough. We can revisit if necessary as we come near the official deprecation date for the Firefox 91 ESR.
 
Mike
 
 
 
Note to self:

https://urldefense.us/v3/__https:/bugzilla.mozilla.org/show_bug.cgi?id=1755368__;!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOekjRTsw$  Version 97.0 don't open JNLP files
https://urldefense.us/v3/__https:/bugzilla.mozilla.org/show_bug.cgi?id=1576762__;!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOh-9zdcc$  Improve usability for JNLP and other executables

On Monday, May 9, 2022 at 3:33:21 PM UTC+2 mailto:mka...@mozilla.com wrote:
We have not allowed JNLP to be opened directly on rapid release for a while now because it's considered an executable. We do allow it on ESR.
 
I'm working on policy changes to allow this on rapid release. It should make the 102 ESR.
 
The Firefox 99 changes were something different.
 
Mike
 

On Fri, May 6, 2022 at 12:29 PM Florent Lagoda <mailto:florent...@univ-rennes2.fr> wrote:
Hi,

Have same behavior here. See the reports here https://urldefense.us/v3/__https:/bugzilla.mozilla.org/show_bug.cgi?id=1754525__;!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOMzZxREg$

I am interested with your policies settings to restore the old behavior
 

Le 03/05/2022 à 18:28, mailto:enter...@mozilla.org a écrit :
https://urldefense.us/v3/__http:/groups.google.com/a/mozilla.org/group/enterprise/t/95791448d60dbeee?utm_source=digest&utm_medium=email__;!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcO5LVHCes$
"André Sänger" <mailto:andre....@landkreis-coburg.de>: May 03 04:14PM +0200

You received this message because you are subscribed to the Google Groups "mailto:enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mailto:enterprise+...@mozilla.org.
To view this discussion on the web visit https://urldefense.us/v3/__https:/groups.google.com/a/mozilla.org/d/msgid/enterprise/d17a6db8-da91-7a58-e546-2b61a4cef34f*40univ-rennes2.fr?utm_medium=email&utm_source=footer__;JQ!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOKbx2XIw$.
--
You received this message because you are subscribed to the Google Groups "mailto:enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mailto:enterprise+...@mozilla.org.
To view this discussion on the web visit https://urldefense.us/v3/__https:/groups.google.com/a/mozilla.org/d/msgid/enterprise/8e48eb5f-1c19-4c32-a431-76cdd483c08cn*40mozilla.org?utm_medium=email&utm_source=footer__;JQ!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOwzRUmxc$.
--
You received this message because you are subscribed to the Google Groups "mailto:enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mailto:enterprise+...@mozilla.org.
To view this discussion on the web visit https://urldefense.us/v3/__https:/groups.google.com/a/mozilla.org/d/msgid/enterprise/6a06059dffa840b790f35a65dc2f95aa*40gsi.de?utm_medium=email&utm_source=footer__;JQ!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOjL26w1U$.
--
You received this message because you are subscribed to the Google Groups "mailto:enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mailto:enterprise+...@mozilla.org.
To view this discussion on the web visit https://urldefense.us/v3/__https:/groups.google.com/a/mozilla.org/d/msgid/enterprise/CAHueOzDQWcLtjNJEuCJMCDxrBPnTYQe9N0SeUDfgaJuy3of*3DpA*40mail.gmail.com?utm_medium=email&utm_source=footer__;JSU!!Az_Xe1LHMyBq19w!aS8AsGMZG9u4G7Hu74AHtxMqy6BPW13U33jlkGnVw03bDbx5zBc9wv7OPLcOaK2MO8A$.
--
You received this message because you are subscribed to the Google Groups "mailto:enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mailto:enterprise+...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/CAHueOzAWua4u_Mppo8V2RHVxk9QwD_vjxRyCEk3E%2BBP6eDef4g%40mail.gmail.com?utm_medium=email&utm_source=footer.

[Mike Kaply]

I'll fix the typo, and good call. I'll add better docs to the Readme.

Mike

You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/a9f01bf14d3648c0901b10f50cc0f6f9%40gsi.de.

[Lanner, Stephan]

Hi all,

until now, I failed to get jnlp started without interaction in FF 102.

 

The site where the jnlp-file is downloaded from is like “https://xy.mysite.at”

 

My GPO looks like:

ExemptDomainFileTypePairsFromFileTypeDownloadWarnings=

[{

"file_extension": "jnlp", "domains": ["mysite.at",https:// mysite.at,"xy. mysite.at",https://xy. mysite.at]

}]

 

But I always get a message-box to store the jnlp-file or cancel the action.

 

What ist wong?

 

Regards,

Stephan

__

Stephan Lanner

Workplace

Bundesrechenzentrum GmbH

[Mike Kaply]

On Mon, Jul 11, 2022 at 2:11 AM Lanner, Stephan <stephan...@brz.gv.at> wrote:

Hi all,

until now, I failed to get jnlp started without interaction in FF 102.

 

The site where the jnlp-file is downloaded from is like “https://xy.mysite.at”

 

My GPO looks like:

ExemptDomainFileTypePairsFromFileTypeDownloadWarnings=

[{

"file_extension": "jnlp", "domains": ["mysite.at",https:// mysite.at,"xy. mysite.at",https://xy. mysite.at]

}]

 

But I always get a message-box to store the jnlp-file or cancel the action.

That policy is to prevent the error when you launch a JNLP, not to allow launching.

Unfortunately I've lost my JNLP testcase so I can't do more testing on this.

Does anyone have a public JNLP file I can use for testing?

Mike

 

 

What ist wong?

 

Regards,

Stephan

__

Stephan Lanner

Workplace

Bundesrechenzentrum GmbH

--

You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/6196de81d8154afdacdcf296cf74365b%40brz.gv.at.

[Pieter Breugelmans]

Stephan is reporting the same issue as I was describing. You can find a public JNLP file here:

https://docs.oracle.com/javase/tutorial/deployment/webstart/examplesIndex.html

https://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp

I too have not found any combination that would automatically launch such JNLP files from Firefox ESR 102.0. Even if you got as far as getting the JNLP mimetype to register in Firefox, AND change to Use Java(TM) Web Launcher (default) then still, it does *not* launch automatically.

This relates to a bug previously created by my colleague, a bug closed as resolved yet in fact Firefox does not behave as expected.

Bug 1738916 Firefox asks for a file location when "always ask me where to save files" is enabled, even if the file is configured always to open in an external app

[Mike Kaply]

OK, sounds like I have more to do here. I'll work on it for the final Firefox 102 ESR.

Mike

[Pieter Breugelmans]

Thanks for acknowledging the issue Mike. As a reference, I've created Bug 1779018 Unable to run JNLP file automatically (FF ESR 102.0).

[Mike Kaply]

So in case folks didn't follow all of the work here, in the end, I wasn't able to get the new policy working as well as it should, so I put the same JNLP bypass into the ESR that was there before.

I'm continuing to try to get a better solution.

Mike

[Pieter Breugelmans]

I'm kindly checking in on this case ahead of the upcoming Firefox ESR this year, since Bug 1779018 remains open since last year when the code changes were reverted.

@Mike, can you advise us whether you plan to revisit this case so that the behavior can be controlled via the ExemptDomainFileTypePairsFromFileTypeDownloadWarnings browser policy?

[Luca Manganelli]

Il giorno gio 19 gen 2023 alle ore 12:07 Pieter Breugelmans <pieter.br...@gmail.com> ha scritto:

I'm kindly checking in on this case ahead of the upcoming Firefox ESR this year, since Bug 1779018 remains open since last year when the code changes were reverted

Is there any update about this bug? This bug is very annoying and we stayed on Firefox 91 in our organization due to this problem.

I don't understand WHY on every ESR new version we, system administration, should pray that all things do their job without managing too complicated policies (like extension handlers).

---

Comune di Trento  via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 00355870221 tel. +39 0461.884111 | www.comune.trento.it

[Mike Kaply]

On Thu, Jan 26, 2023 at 3:08 AM Luca Manganelli <luca.ma...@comune.trento.it> wrote:

Il giorno gio 19 gen 2023 alle ore 12:07 Pieter Breugelmans <pieter.br...@gmail.com> ha scritto:

I'm kindly checking in on this case ahead of the upcoming Firefox ESR this year, since Bug 1779018 remains open since last year when the code changes were reverted

Is there any update about this bug? This bug is very annoying and we stayed on Firefox 91 in our organization due to this problem.

My currently plan is to continue to make JNLP work on the ESR. Unfortunately making the necessary changes to Firefox became entirely too complicated.

 

I don't understand WHY on every ESR new version we, system administration, should pray that all things do their job without managing too complicated policies (like extension handlers).

We have made JNLP work in the 102 ESR so there's no need to stay on Firefox 91.

Mike Kaply

 

---

Comune di Trento  via Belenzani, 19 - 38122 Trento | C.F e P. IVA: 00355870221 tel. +39 0461.884111 | www.comune.trento.it

--

You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/CAGKduJ2yfmT12ntjNsj4PJLkeFiD4ofbCf1mJztWGus%2Bd_XQnA%40mail.gmail.com.

[Mike Kaply]

On Thu, Jan 19, 2023 at 6:07 AM Pieter Breugelmans <pieter.br...@gmail.com> wrote:

I'm kindly checking in on this case ahead of the upcoming Firefox ESR this year, since Bug 1779018 remains open since last year when the code changes were reverted.

@Mike, can you advise us whether you plan to revisit this case so that the behavior can be controlled via the ExemptDomainFileTypePairsFromFileTypeDownloadWarnings browser policy?

At this point, I'm just going to enable JNLP on the ESR again.

The problem is that in order for the policy to work, we have to have the domain and in various places where we handle file extensions, and we simply don't.

I couldn't find a clever way to retrofit things into Firefox.

Also, the policy

ExemptDomainFileTypePairsFromFileTypeDownloadWarnings

has been deprecated by the other browsers. I'm going to investigate if the replacement is any better.

Mike Kaply

[Mike Kaply]

> has been deprecated by the other browsers. I'm going to investigate if the replacement is any better.

Nevermind, It looks like the replacement is just a rename due to a type error.

Mike

[Luca Manganelli]

Il giorno gio 26 gen 2023 alle ore 14:35 Mike Kaply <mka...@mozilla.com> ha scritto:

> We have made JNLP work in the 102 ESR so there's no need to stay on Firefox 91.

Thank you, in which 102.x sub-version?

[Ryan VanderMeulen]

102.2esr

--

You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/CAGKduJ1ji2pHc7n69vfxhK%3DxeskAUQwFK_a%2BcHwm4Y8%2BFXAhQQ%40mail.gmail.com.

[Pieter Breugelmans]

Bug 1785830 Port bug 1722314 (JNLP) to 102 ESR.

--> "Approved for 102.2esr"