Brandon H Supervisor Share Posted June 17, 2010 what do you think, is this a fail on the part of google chrome Link to post Share on other sites
0 Chasethebase Veteran Share Posted June 17, 2010 Even though this is a messup probably, it helps to prevent you hitting false URLs. Link to post Share on other sites
0 KoL Veteran Share Posted June 17, 2010 Same thing happened to me the other days. Link to post Share on other sites
0 Fred Derf Veteran Share Posted June 17, 2010 remove the Https:// :p Yeah, that is the problem but Chrome should provide a more helpful error message. Link to post Share on other sites
0 NzOMikE Share Posted June 17, 2010 OUPS DOUBLE... Chrome fail ahah. Link to post Share on other sites
0 Brandon H Author Supervisor Share Posted June 17, 2010 remove the Https:// :p there was no https://, i just clicked a related video in youtube to go to the next part of the video :p Link to post Share on other sites
0 brian_mi Share Posted June 24, 2010 https gives another screen. youtube must has google analystics script on its webpages to record visits of the website. but it never happens on my pc. Link to post Share on other sites
0 NoneAvail Share Posted June 24, 2010 Haha, sometimes that **** gets annoying though, I have eset antivirus and it blocks certain pages where I *KNOW* its a safe site, just cause someone reported it or whatever doesn't let me view it until i turn the feature off. Link to post Share on other sites
0 -=Outlaw=- Share Posted June 24, 2010 Thread Title Fail? lol 1 Share Link to post Share on other sites
0 Skulltrail Share Posted June 27, 2010 there was no https://, i just clicked a related video in youtube to go to the next part of the video :p Looks like you removed the protocol (http, https, ftp, etc.). Chrome, and every browser out there, will automatically enter a protocol if you just enter "www.youtube.com" ("http" by default). Would have looked more realistic if you didn't remove the "https://" and instead replaced it with "http://" Link to post Share on other sites
0 fhpuqrgrpgvirzhpujbj Share Posted June 27, 2010 Looks like you removed the protocol (http, https, ftp, etc.). Chrome, and every browser out there, will automatically enter a protocol if you just enter "www.youtube.com" ("http" by default). Would have looked more realistic if you didn't remove the "https://" and instead replaced it with "http://" My chrome doesn't even show the www... Link to post Share on other sites
0 TechFreak:) Share Posted June 27, 2010 Actually it should look like this: It happens because Google uses the same ip for google.com and youtube.com. And they use SSL certificate which is valid only for *.google.com. Link to post Share on other sites
0 Singh400 Share Posted June 27, 2010 Looks like you removed the protocol (http, https, ftp, etc.). Chrome, and every browser out there, will automatically enter a protocol if you just enter "www.youtube.com" ("http" by default). Would have looked more realistic if you didn't remove the "https://" and instead replaced it with "http://" No, Google Chrome now removes http:// and keeps just www. Unless it is https:// or something else. Link to post Share on other sites
0 Skulltrail Share Posted June 27, 2010 No, Google Chrome now removes http:// and keeps just www. Unless it is https:// or something else. Really now. What version? How do I get Chrome to do this? (3rd-party software) Considering my latest version of Chrome does not do this. If by "removes" you mean grays out the protocol, you can clearly still see it, so it isn't removed at all. EDIT: Looked into it and it was a proposed idea back in April 2010. But it was obviously discontinued in newer versions, such as the latest 5.0.375.86 build. Link to post Share on other sites
0 Singh400 Share Posted June 27, 2010 Really now. What version? How do I get Chrome to do this? (3rd-party software) Considering my latest version of Chrome does not do this. If by "removes" you mean grays out the protocol, you can clearly still see it, so it isn't removed at all. EDIT: Looked into it and it was a proposed idea back in April 2010. But it was obviously discontinued in newer versions, such as the latest 5.0.375.86 build. Screenshot below... Click here if you can't see the above screenshot. Link to post Share on other sites
Question
what do you think, is this a fail on the part of google chrome
Link to post
Share on other sites
19 answers to this question
Recommended Posts