In Firefox, the user can easily apply exceptions to HTTPS-only mode.
https://support.mozilla.org/en-US/kb/https-only-prefs
However, in Firefox for Android, it's an all-or-nothing approach for HTTPS-only mode.
https://support.mozilla.org/en-US/kb/https-only-mode-firefox-android
This has been bugging me ever since HTTPS-only mode was introduced because every time I check Australia's Bureau of Meteorology site for weather forecasts, I have to disable HTTPS-only mode and then I get redirected to http://www.bom.gov.au/akamai/https-redirect.html anyway.
Yes, it's a poor site implementation but until and unless BoM adopts HTTPS, I'm forced to choose between HTTPS-only mode or not at all in Firefox for Android. Is it reasonable to have the Android version match the desktop version or are there technical reasons why this hasn't been implemented? Should I revert to HTTPS Everywhere for Android version only?
Thanks for your consideration.