Extension always uses https despite configuring http

[fidelski]

I am working in a work environment where I want to use the inhouse installation of Kroki. We use this without ssl since our services are not reachable from the internet, we use those services inhouse only.
I therefore configured the extension to point to http://kroki.ours.local:8000. Now I get an error because the extension nevertheless uses https and obviously cannot reach the server.

Configuration: http://kroki.ours.local:8000
Extension tries to accesss: https://kroki.ours.local:8000

[ggrossetie]

I cannot reproduce this issue:

working.mp4

Could you please share additional information?

[fidelski]

Thanks for your investigation! Could it be that you are trying to access localhost and that's why there is no attempt to use ssl? This makes me think that it's not the plugins fault but the browser trying to always use ssl instead of plain http. 🤷‍♂️

[ggrossetie]

Might be something specific to Firefox since I cannot reproduce in Chrome... 🤔

[DrPiWork]

I have the same problem with Firefox 144.02

I investigated and found the source of the problem.
Everything is explained here.

Curiously, the French version of the same page do not have the exact same content.

If I understand correctly what is explained in these pages, the http to https upgrade should not occur with file:/// urls types. Reality says the opposite.

The French version of the page explains how to deactivate the http to https upgrade for passive resources :
In Firefox, open a about:config page, then switch security.mixed_content.upgrade_display_content to False.

Of course, this means this is also deactivated for external websites, opening a potential security vulnerability (?).