Linked by Thom Holwerda on Sun 18th Apr 2010 11:57 UTC, submitted by Anonymous
Google Now this is something that I find really interesting. We all know and love Google Chrome/Chromium (and if you don't, you're demonstrably wrong), but Google recently made a change in the developer version that ruffled some feathers: the URL field will no longer show the "http://". This made a lot of people very upset.
Permalink for comment 419594
To read all comments associated with this story, please click here.
What about port numbers?
by raboof on Sun 18th Apr 2010 13:44 UTC
raboof
Member since:
2005-07-24

When visiting a http site, the port number is usually ':80' - you can specify another one if you wish, but if you leave it out it'll be ':80'.

It makes sense to do the same for the protocol in a web address: you can specify another one, but it'll usually be 'http://', so in that case it doesn't have to be shown.

The only inelegant part is that http and https are both common. OTOH, it's quite rare these days to have the *same* site available both secured and unsecured - usually the unsecured url just redirects to the secured version - so we can hide both 'http' and 'https' and use the 'lock' icon to show the difference.

Reply Score: 4