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

wm4 nfxjfg at googlemail.com
Sun Feb 2 18:12:58 CET 2014

On Sun, 2 Feb 2014 17:51:36 +0200
Andrey Utkin <andrey.krieger.utkin at gmail.com> wrote:

> > Also, IMHO, http.c shouldn't mess with URLs that are perfectly valid.
> 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.

So every tool that uses http out there is unreasonable, misleading,
and surprising? Try spaces in an URL with wget or any web browser, and
see what happens. Try mixing percent encoding and freestanding '%'
characters too.

> It is sufficiently simple for WWW user to get the concept of
> urlencoding. IMO disabled-by-default option for urlencoding would be
> acceptable.

Only a programmer can say something like this.

More information about the ffmpeg-devel mailing list