 | | Re: Growth
|
| (...) This URL didn't work for me, I get an "unrecognized request" response. If I use: (URL) works just fine. Is the first form supposed to work? (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) Yes, the first form is supposed to work -- and I think the problem you're seeing with it is the first ever reported. I'm not surprised, though, because it's technically kind of "dangerous" (or "iffy") to use colons in URLs, because they're (...) (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) Ah, figured it out, if I cut and paste it it works. The whole URL is highlighted in the news article, so I think NS 3.0 has a bug in clicking on the link from the news article. Clicking on the "view raw" link from the HTML version works also (...) (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) You mean that NS 3.0 on AIX/X11 thinks that the trailing > is part of the URL? Wow, I thought only MSOE had that problem. Well, that's good to know. --Todd (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) it's trying to open the url (URL) port 8265, probably. isn't that part of the standard? (24 years ago, 2-Nov-00, to lugnet.admin.general)
| | | | | 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
|
| (...) No, it's highlighting the right part. Hm, if I right click and select "Copy this link location to clipboard" it gets the right thing. Hmm, if I right click and select "Open this link" it puts the right URL into a browser window, but still gets (...) (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
|
| (...) ?? The port has to right after the resource, as in (URL) so I thought, anyway. ++Lar (24 years ago, 3-Nov-00, to lugnet.admin.general)
| | | | | Re: Growth
|
| (...) It appears so. :) Unfortunately not everyone plays along with the standards. (24 years ago, 3-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)
| | | | | Re: Growth
|
| (...) Todd Lehman. :) (24 years ago, 3-Nov-00, to lugnet.admin.general)
| | | | | 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)
| |
