Based on @[email protected]’s comment, maybe some browsers interpret a bare hostname without protocol specifier as an http address, and some as an https address.
maybe some browsers interpret a bare hostname without protocol specifier as an http address, and some as an https address.
And if you have a browser that does the former I would suggest finding a better one soon. The internet is moving away from unencrypted HTTP, a browser that doesn’t default to HTTPS nowadays is pretty strange.
While I do mostly agree with your statement, it’s incredibly annoying when I type in a local IP for my router or server and it automatically gets turned into https.
When I try going to txdmv.gov, I don’t get the same server, but I do go to a machine that http-redirects my browser to www.txdmv.gov.
EDIT: Ah, apparently it redirects http://txdmv.gov/, but not https://txdmv.gov/.
considers
Based on @[email protected]’s comment, maybe some browsers interpret a bare hostname without protocol specifier as an http address, and some as an https address.
Holy shit. This is really good to know… Thanks
And if you have a browser that does the former I would suggest finding a better one soon. The internet is moving away from unencrypted HTTP, a browser that doesn’t default to HTTPS nowadays is pretty strange.
While I do mostly agree with your statement, it’s incredibly annoying when I type in a local IP for my router or server and it automatically gets turned into https.