 | | Re: Growth
|
| (...) No -- the port goes immediately after the domain or machine name, not at the end of the URL. --Todd (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) Although I've come across many client applications that don't get it right; xmms is the first one that comes to mind, as it assumes anything after a colon in the URL is a port number, no matter where it shows up. Chris (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) wow, so a properly formed (URL) won't work? That's pretty bad. (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) I probably didn't explain it right... The example that you give above works, but something like (URL) because it thinks that song.mp3 is the port number. Other failures include (URL) it would try to connect on port 100. As Todd pointed out, (...) (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) Yah, I mentioned this a long time ago (URL) but no one cared. :) The ':' character (unlike '~', which is merely unsafe) is labeled "reserved". Like '/' or '?', it is only supposed to be used in certain ways. So really, xmms is doing the right (...) (24 years ago, 3-Nov-00, to lugnet.off-topic.geek)
| | | | | Colons in URLs (was: Re: Growth)
|
| (...) Okie dokie, I just fixed the page-generating scripts that were using ":" in the URLs. I switched the to commas "," . (Colon ":" still works of course for sdrawkcab compatibility. :-) --Todd (24 years ago, 4-Nov-00, to lugnet.off-topic.geek, lugnet.admin.general)
| | | | | Re: Colons in URLs (was: Re: Growth)
|
| (...) :) (24 years ago, 4-Nov-00, to lugnet.off-topic.geek, lugnet.admin.general)
| |
