Re: [PATCH] wget.py: support for semi-colons in URL

[Olof Johansson <olof.johansson@axis.com>]

Excerpts from Peter Urbanec's message of 2015-07-28 07:47:17 +0200:
> I have not examined the code, but could the URL use the standard URL 
> encoding mechanism to represent ; as %3B ?
> 
> The idea being that the initial "Bitbake URL" is parsed / split using 
> the original string with semicolons and the URL escaped semicolon is 
> passed through to a lower layer that uses that part of the string as an 
> "Internet URL"

URI encoded enitities today are handled correctly in my opinion. If I
have a filename including a ;, I don't want it to be parsed as part of
the URL, neither by bitbake nor the remote server --- that's where URI
encoding comes in.

By hijacking URI encoding to mean "part of the URI, not parsed by
bitbake", you will suprise users that expect it to mean "URI data, not
URI control character" if I understand your proposal correctly.

That could be solved by double encoding, but I don't think that would be
worth it, all occurences of URI encoding in SRC_URI today would have to
be updated. E.g. %20 -> %2520.

-- 
olof johansson