Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Have a DigiCert signed .jar-doesn't work in V53, does work in IE 11& V52. Firefox is shorting the includes path with a 404 error under Inspector, needs fixing!

  • 1 réponse
  • 1 a ce problème
  • 15 vues
  • Dernière réponse par Kohei

more options

I have a DigiCert Code signed .jar file that doesn't work in V53 but does work in IE 11& V52. Firefox ESR. Firefox is shorting the location of the includes path by ones level for the .jar with a 404 error under Inspect Element->Network. This appears to be fault in the browser and needs fixing. It also somewhat weird that the .jar file is being shown as an html file and not a script. Something is not right in the V53 version as the identical code and certificate store runs under Internet Explorer and also in Firefox V52 ESR. The issue is both on Windows 7 and Windows 10 machines

Without a correction, I have customers that prefer to use Firefox but this fault is making it impossible for me to use V53.

I have a DigiCert Code signed .jar file that doesn't work in V53 but does work in IE 11& V52. Firefox ESR. Firefox is shorting the location of the includes path by ones level for the .jar with a 404 error under Inspect Element->Network. This appears to be fault in the browser and needs fixing. It also somewhat weird that the .jar file is being shown as an html file and not a script. Something is not right in the V53 version as the identical code and certificate store runs under Internet Explorer and also in Firefox V52 ESR. The issue is both on Windows 7 and Windows 10 machines Without a correction, I have customers that prefer to use Firefox but this fault is making it impossible for me to use V53.

Toutes les réponses (1)

more options

This is probably Bug 1361688 which has already been fixed with Firefox 54.