4 ms·
My best guess. From RFC 3986 (link below) For example, the semicolon (";") and equals ("=") reserved characters are often used to delimit parameters and par
by daveslash 12y ago
My best guess. From RFC 3986 (link below)
For example, the semicolon (";") and equals ("=") reserved characters are
often used to delimit parameters and parameter values applicable to
that segment. The comma (",") reserved character is often used for
similar purposes. For example, one URI producer might use a segment
such as "name;v=1.1" to indicate a reference to version 1.1 of
"name", whereas another might use a segment such as "name,1.1" to
indicate the same.
http://www.ietf.org/rfc/rfc3986.txt http://www.ietf.org/rfc/rfc3986.txt
EDIT: This RFC is for URIs and your question was about URLs. URLs are generally considered a subset of URIs, but according to this SO answer, that might be open to debate. http://stackoverflow.com/questions/176264/whats-the-difference-between-a-uri-and-a-url http://stackoverflow.com/questions/176264/whats-the-differen...
- tronium 12y agoThanks dave, that helped explain a little. However, I still have never actually seen a comma used as a parameter in a URL, do you have an example?
- mcintyre1994 12y agoThe only case I can remember, and I'm not even sure why I remember is it was used as a delimiter in the Runescape forums. Just checked and it still seems to be, eg http://services.runescape.com/m=forum/forums.ws?185,186,980,60829426 http://services.runescape.com/m=forum/forums.ws?185,186,980,...
- randallma 12y agoThe Onion has their article urls in the format: http://www.theonion.com/articles/scientific-community-baffled-by-man-whose-waist-32,36157/ http://www.theonion.com/articles/scientific-community-baffle... /articles/slug,id/
- daveslash 12y agoWow, thanks, I don't think I'd ever noticed a URL with a comma. I don't think it's a valid* URL, but apparently it's definitely do-able. *valid == conforming to spec.
- daveslash 12y agoSorry for the late response. I don't have an example, sorry. Commas should not be used in URLs because they are so frequently used as delimiters in other scenarios. That's not to say that it can't work (so I'm sure there are some URLs with commas), but according to that RFC we shouldn't use them. Any URL with commas in it would be in violation of that spec. But hey, this is the web, we like to break specs all the time! ;-) It's my impression that this is more for sanity reasons than technical limitations.