I thought using colons in URIs was "illegal". Then I saw that vimeo.com is using URIs like http://www.vimeo.com/tag:sample.
It's just a separator. It doesn't 'mean' or 'specify' anything. In your own example it is also used to separate the scheme from the hostname.
Not only do they exclude valid characters like semicolons and parentheses, that last one matches all kinds of invalid characters like quotation marks, braces, and non-ASCII characters.
A URL is composed of a limited set of characters belonging to the US-ASCII character set. These characters include digits (0-9), letters(A-Z, a-z), and a few special characters ( "-" , "." , "_" , "~" ). When these characters are not used in their special role inside a URL, they must be encoded.
Answer: While it's definitely possible to use commas in URLs, it's not a widely used practice, nor is it recommended. When it comes to most online users, anything out of the ordinary can make them wary of a Web site. And with our example above, just seeing a comma-delineated URL may cause site visitors to click away.
Colons are allowed in the URI path. But you need to be careful when writing relative URI paths with a colon since it is not allowed when used like this:
<a href="tag:sample">
In this case tag
would be interpreted as the URI’s scheme. Instead you need to write it like this:
<a href="./tag:sample">
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With