Garmin's behaviour is inconsistent with expected user behaviour in 2025
And I find that it is a very wise decision of Garmin, because using the HTTP protocol as default will not harm practically any website using only HTTPS, since they (in very most cases) use a permanent redirect from HTTP to HTTPS anyway. In contrary, if Garmin used HTTPS by default, it would render plenty of links to websites without the SSL support (or with a misconfigured certificate) inoperable.
So I insist, that the way it works is exactly as it was intended, and all right even in 2025.
The problem for me initally was i didnt know I would write https:// first in order to show it https://. Its was not obvious for me. But now I know how it work, you write https// first and then it shows correct.
