Google to Remove http:// From Future Chrome

Status
Not open for further replies.

acecombat

Distinguished
Apr 2, 2009
213
0
18,680
0
[citation][nom]the_one111[/nom]How will I know websites are encrypted with Https then?[/citation]
Please read before making a comment:
A problem could come up with trying to access ftp or https, though it seems that the upcoming Chrome will still display those when applicable.
 

pojih

Distinguished
May 21, 2009
158
0
18,680
0
Most of the time on Chrome I just type in "toms hardware" and either google will pull it up, or it comes straight here.
 

dotaloc

Distinguished
Jul 30, 2008
319
0
18,810
12
[citation][nom]brendano257[/nom]I only type "tomshardware.com" etc. Haven't done anything differently for years, except for FTP or HTTPS of course...[/citation]

+1 to that. i was thinking it as i read each comment and relieved that i wasn't the only one. i think my next batch of business cards are going to omit http://(used currently) and www(haven't used in a while).
 

kelemvor4

Distinguished
Oct 3, 2006
469
0
18,780
0
probably not a great idea on the www since www.domain.com is just a subdomain of domain.com and not necessarily the same IP at all.

On the other hand, I don't really care what Google does. I tried chrome and didn't like it.
 

Zinosys

Distinguished
Jul 12, 2009
453
0
18,810
9
http:// and www. are two totally different things. http:// is specifying the protocol to use when transferring the data from server to client, and www. is a subdomain of the web server you are going to.

Except for ftp://, https://, smb://, and afp://, I type tomshardware.com. :D
 
G

Guest

Guest
I don't understand this change at all. The http:// is an important part of the address. So, it won't display the http://, but it will display the https://??? Just display the whole thing. Don't be dicks, Google.
 

nottheking

Distinguished
Jan 5, 2006
1,456
0
19,310
16
Yeah, this makes little sense to me. And will likely drive many of the more tech-savvy from Chrome, and instead to their closest competitor, Opera. (then again, Opera's what I personally use)

But yeah, there's a REASON there's still "Http://" and it's not due to legacy. As others have already noted, it's to differetiate it from other protocols used on the Internet, most commonly (in browsers) "https://" and "ftp://," and perhaps less commonly, ones like "irc://", "smb://" or even "afp://" It's a strong sense of inconsistency to remove it for one protocol, and keep it for the rest.

TBH, this is just taking Chrome another step toward being the "baby's browser," and less of one made for people with actual tech-savvy.
 
Status
Not open for further replies.

ASK THE COMMUNITY