Massassi Forums Logo

This is the static archive of the Massassi Forums. The forums are closed indefinitely. Thanks for all the memories!

You can also download Super Old Archived Message Boards from when Massassi first started.

"View" counts are as of the day the forums were archived, and will no longer increase.

ForumsDiscussion Forum → Ze Slashes! ZE DO NOTHINK
Ze Slashes! ZE DO NOTHINK
2009-10-14, 6:39 PM #1
http://bits.blogs.nytimes.com/2009/10/12/the-webs-inventor-regrets-one-small-thing/

ha. I KNEW IT
Holy soap opera Batman. - FGR
DARWIN WILL PREVENT THE DOWNFALL OF OUR RACE. - Rob
Free Jin!
2009-10-14, 9:01 PM #2
I think // is supposed to mean "next we specify the server name". If it was a single / it would mean: "the following is a full path on the current server" and a lack of a beginning / means "the following is a relative path on the current server from the currently displayed file".

So if you just did "https:." you'd jump to the same page on HTTPS. Of course with a protocol, modern OSs/browsers only support the // syntax and neither of the others, hence why it's really unnecessary.

I came to this conclusion because paths on Windows machines work the same way. \\computername\share and all that. For samba shares on linux you use smb://computername/share.

Hmm I wonder if you can use "//www.google.com/" etc syntax in HTML links?

[Edit: HA! Google Chrome at least supports it! I made a link that goes to google.com using whatever the current protocol is!]

↑ Up to the top!