| |
> > 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.
>
> wow, so a properly formed http://x.y.z:1234/a/b/c won't work? That's
> pretty bad.
I probably didn't explain it right... The example that you give above
works, but something like
http://www.example.com/track-a:song.mp3
fails because it thinks that song.mp3 is the port number. Other failures
include
http://www.example.com/view/image/mylego.jpg?1000:100
where it would try to connect on port 100.
As Todd pointed out, the colon should be replaced with %3A, but that
doesn't excuse poor matching like this. :)
Chris
FUT: lugnet.off-topic.geek
|
|
Message has 1 Reply:
 | | 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)
|
Message is in Reply To:
28 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
