http and www added to address
Categories
(Firefox for Android :: General, defect)
Tracking
()
People
(Reporter: csadilek, Unassigned)
Details
From github: https://github.com/mozilla-mobile/fenix/issues/19510.
Steps to reproduce
Enter address
http://thisisnotarealhost.local/
.Actual results
Firefox changed address to
https://www.thisisnotarealhost.local/
, then reported that the web site is unreachable.Note the change includes both use of the secure protocol (
https
) and a web sub-domain (www
).Expected results
Firefox should have preserved the address, and perhaps merely suggested changing it.
The real case is a simple one. A user seeks to connect to a local appliance, at some time when it is not operational. Realizing that the endpoint is unreachable, the user sets the appliance to be operational, then attempts to to reconnect. The address registered in the browser, however, is not correct.
In this case, the appliance uses a basic local domain, not a fully-registered web domain leading with
www
, or using a secure certificate. Such a case is very common for local systems, particularly small devices. Firefox must not assume that an address follows some canonical form for a full web site, even following a failure to reach a host using an address not in this form.In recent use, I attempted to debug a small device operating on a simple local domain, and repeatedly needed to restore the address to the original form, changing
https
back tohttp
and removing the leadingwww
. The behavior was tremendously frustrating, and makes Firefox essentially unusable for this simple task.Device information
This problem reproduces in version 88.1.3 on Android. I am running Havoc-OS 2.8 (based on AOSP 9) on a Google Pixel 3.
┆Issue is synchronized with this Jira Story
Change performed by the Move to Bugzilla add-on.
Comment 1•2 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
I cannot reproduce this anymore. QA, please validate. Thank you!
Updated•2 years ago
|
Comment 3•2 years ago
•
|
||
Hello, I was not able to reproduce the issue on the latest Nightly build from 15th of June 2023 (116.0a1).
Tested on Google Pixel 7 Pro (Android 13)
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•