This is a long, sad story. You see, in the beginning of time, browsers replaced the space character with the plus character. Then people wanted plus characters and other "special" characters, like non-ASCII characters in their URIs. So urlencoding was born.
Some severly brain-damaged browsers and servers still don't deal with this correctly.
*_Usually,_* you can deal with this by *_double-urlencoding_* the URL/URI.
For the JW FLV Media Player, all URL/URIs that have the special characters ( ? = & ), *MUST* be urlencoded because those characters are also used to assemble the flashvars string.
So you can see that the special characters within the URI are urlencoded, but the special characters that are used to assemble the flashvars string are NOT urlencoded.
Now back to the brain-damaged...
Some browsers and/or servers will un-urlencode the string, messing things up.
One way to deal with this is to *double-urlencode* the string.
Unfortunately, I can't get the position/length numbers to display properly after rebuilding the project. I downloaded the right font (I think - it didn't throw any missing font errors). They're offset vertically.
Well, I traded it for another - the position/length number display issue. if anyone knows how to fix the font issue (I downloaded the suggested one) and insert that one line of code above, I'd be very thankful... my e-mail is nathanael.jones at gmail.com.
@lefTY Yeah, I think the latest version of Wowza now requires URL encoding - I guess the 4 you listed don't.
The filenames are URL decoded at the beginning, so I don't see any reason why URL encoding them should cause a compatibility issue. And official word on this issue? Any patch date?
This question has received the maximum number of answers.