Open radusun opened 5 years ago
This is intentional behavior. It is not possible to obtain a widely accepted SSL certificate for IP addresses, so most connections to a IP address over https would almost always fail.
Why not to choose what user want ?
Because of limitations in the extension API, I am not actually able to see whether you have entered just an IP or actually an IP with http://
in front of it in the url bar. The extension does some smart guessing and will redirect navigations that are not initiated by web pages (urlbar, history, bookmarks, etc.), and because most sites support https, this works nicely.
However, IP addresses rarely have certificates, so redirecting these URLs often result in a worse user experience. Due to the uncertainty and the low likelihood of success, I choose to intentionally ignore IP addresses.
I'm willing to consider adding an option to redirect IP addresses, but I'm not sure if it is of much use. @pschonmann Is this request of the category "it would be nice if XXX" (implyfing that you wouldn't use the feature) or "I really want XXX" (meaning that you do have an actual use case)?
PS. This extension can more easily be implemented as a built-in part of Firefox, and there are signals that a request for it may be viable, so I opened a feature request at https://bugzilla.mozilla.org/show_bug.cgi?id=1628831
If I type (or paste in) an IP address, (e.g. ###.###.###.###) it defaults to http whereas I would expect to default it to https.
Can you check? Thanks!