On Wed, 24 Aug 2011, warp.kawada_at_gmail.com wrote:

> This patch allows curl to be able to send the custom headers with empty
> value. I badly need this function, but now latest curl can not.

Thanks!

I do however think that an additional space (or more) is too subtle to signal
this to libcurl, not to mention that there may already be existing apps that
depend on the fact that a space or not after the colon doesn't make a
difference.

In order to not to break existing apps, we need to introduce this ability so
that old apps keep working and new apps don't do this by accident.

I would then suggest that we for example allow the header to get added
completely without a colon or possibly by using another symbol than the colon
(semicolon?) to instruct libcurl about it. Something that there's zero risk an
existing app would do.

Thoughts?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html