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 ».

Learn More

Connecting to non-ssl site on localhost failing after upgrade to 108

  • 2 réponses
  • 0 a ce problème
  • 5 vues
  • Dernière réponse par Dropa

more options

I have a local app on my machine hosted on port 80 using a non-encrypted HTTP connection. Tonight I upgraded my Firefox browser to version 108 and I cannot for the life of me figure out how to allow this connection. Before the upgrade, it worked perfectly fine, after the upgrade it tells me it was unable to connect but in the address bar I see that it's trying to connect to HTTPS Even though the bookmark is HTTP. If I remove the s from the address bar, it still refuses to connect. The chromium-based browser on my computer will connect to this site without any trouble, as will the legacy browser. This seems to be a problem introduced in version 108 and I have no way around it. Has anybody else experienced this problem? I don't want to write a sloppy bug report so I'll probably just wait for someone important to have this problem and the next release will probably have it fixed, but it's pretty annoying having to open up my chromium based browser in order to access this one local URL.

I have a local app on my machine hosted on port 80 using a non-encrypted HTTP connection. Tonight I upgraded my Firefox browser to version 108 and I cannot for the life of me figure out how to allow this connection. Before the upgrade, it worked perfectly fine, after the upgrade it tells me it was unable to connect but in the address bar I see that it's trying to connect to HTTPS Even though the bookmark is HTTP. If I remove the s from the address bar, it still refuses to connect. The chromium-based browser on my computer will connect to this site without any trouble, as will the legacy browser. This seems to be a problem introduced in version 108 and I have no way around it. Has anybody else experienced this problem? I don't want to write a sloppy bug report so I'll probably just wait for someone important to have this problem and the next release will probably have it fixed, but it's pretty annoying having to open up my chromium based browser in order to access this one local URL.

Modifié le par Nathaniel Lee

Toutes les réponses (2)

more options

(deleted duplicate)

Modifié le par Nathaniel Lee

more options

Without providing a URL of the site no one is going to know just from reading what is going on.