On Thu, 25 Sep 2008, Igor Novoseltsev wrote:

> The "really wild" API forces an application to perform URL encoding. For
> now, my application is simply enough to not bother with encoding at all. May
> be there are other applications that don't deal with encoding.

Well, libcurl provides a function to do the URL encoding so it would not
exactly be hard for an app to encode whatever name it wants.

> While taking in account that the patched code can be easily extended in
> future to work with byte array, I would prefer not to work on this now, when
> no specific requirement arose.

But introducing encoded names in the future will then require another set of
arguments or break the ABI and that would be an excessive amount of options
for the same things. Of course nobody ever asked for being able to include
zeroes in these fields so it's not really a big deal.

-- 
  / daniel.haxx.se