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

Nicolas George george at nsup.org
Sun Feb 2 17:59:26 CET 2014

Le quartidi 14 pluviôse, an CCXXII, Andrey Utkin a écrit :
> But you want to do it. As i have said earlier, if query already
> contains sth like %20, you cannot know whether it is already
> urlencoded or not, if you don't ask user.
> Leaving %-stuff untouched and replacing only spaces is not acceptable
> as i stated above. ffmpeg behaviour would be misleading and results
> would be surprising. Surprises (even pleasant at some situations)
> should be avoided in engineering.
> It is sufficiently simple for WWW user to get the concept of
> urlencoding. IMO disabled-by-default option for urlencoding would be
> acceptable.

For what it's worth, I completely agree with you. The task of correctly
encoding the URL should fall on the process that created the URL in the
first place.

If some process were known to frequently produce invalid URLs, then we could
consider adding a workaround, but for now this is just idle talk.


  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140202/1aa51baa/attachment.asc>

More information about the ffmpeg-devel mailing list