[FFmpeg-devel] [PATCH] http: handle URLs with spaces

[Eli Kara]

>Could you please try actually reading >what I wrote? There is no way encoding >a space character can result in double >encoding, period. It is _absolutely_ _impossible_ for that to break anything >compared to now (assuming no server >that actually wants broken URLs and >assuming you're not trying to write >server exploits...)

You cannot encode only spaces and if you want to encode all invalid chars this is tricky as said before. Ex:

foo%20bar, a previously encoded URL becomes foo%2520bar ==> unplayable. 

My whole point was that this couldn't be done blindly, even if your algorithm is good like wget's. 

That's just my opinion of course.