Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Basic auth stopped working

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan ken155

ken155
ken155
more options

I use Firefox to develop my organization's CMS, which uses HTTP Basic Auth. This stopped working suddenly - no basic auth prompt is shown as of 16 Feb 2022. There's no error in the window or console, my server logs a 401 as expected but I've no way to log in. It works fine on other browsers.

Presumably, this is due to the fact that the CMS runs on HTTP, not HTTPS.

Is there anything I can do? We need to keep this running on port 8080...

I use Firefox to develop my organization's CMS, which uses HTTP Basic Auth. This stopped working suddenly - no basic auth prompt is shown as of 16 Feb 2022. There's no error in the window or console, my server logs a 401 as expected but I've no way to log in. It works fine on other browsers. Presumably, this is due to the fact that the CMS runs on HTTP, not HTTPS. Is there anything I can do? We need to keep this running on port 8080...

Bewurke troch ken155 op

Keazen oplossing

Dev I am not, but are you currently using your distro version of Firefox? Try downloading another copy from Mozilla and see if you have the same issue.

https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

jonzn4SUSE
jonzn4SUSE
  • Top 10 Contributor
more options

Keazen oplossing

Dev I am not, but are you currently using your distro version of Firefox? Try downloading another copy from Mozilla and see if you have the same issue.

https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

ken155
ken155 Fraacheigener
more options

@jonzn4SUSE, if you are telling me that this is not a new Firefox behavior, sure I can try that. I just assumed it was, albeit a bit heavy-handed...